View Issue Details

IDProjectCategoryView StatusLast Update
0008158Kali LinuxGeneral Bugpublic2023-02-23 01:39
Reportercaesarcipher Assigned Toarnaudr  
PrioritynormalSeverityblockReproducibilityalways
Status resolvedResolutionfixed 
Product Version2022.4 
Summary0008158: Live-Builds Fail in Debian Environments
Description

I followed the directions from https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment to configure an Ubuntu Server instance to be able to produce the Kali ISO. It worked for a while, but has been failing since sometime in November. I tried building the same project from Kali and it works without issue. I have been needing to open this ticket for a while and been putting it off, so sorry if all the required information is not present; I can provide additional details as needed.

The end of the build.log file when the build fails on the Ubuntu system contains the following:

Reading state information...
[2022-11-15 21:43:48] lb binary_linux-image
P: Begin install linux-image...
[2022-11-15 21:43:49] lb binary_memtest
P: Begin installing memtest...
Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
grub-pc | grub-legacy memtester mtools
The following NEW packages will be installed:
memtest86+
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 122 kB of archives.
After this operation, 13.0 MB of additional disk space will be used.
Get:1 http://kali.download/kali kali-rolling/main amd64 memtest86+ amd64 6.00-1 [122 kB]
Fetched 122 kB in 0s (880 kB/s)
Selecting previously unselected package memtest86+.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 436316 files and directories currently installed.)
Preparing to unpack .../memtest86+_6.00-1_amd64.deb ...
Unpacking memtest86+ (6.00-1) ...
Setting up memtest86+ (6.00-1) ...
cp: cannot stat 'chroot/boot/memtest86+.bin': No such file or directory
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
Build of kali-rolling/vm/amd64 live image failed (see build.log for details)

Steps To Reproduce

configure Ubuntu environment per instructions at https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment
git clone https://gitlab.com/kalilinux/build-scripts/live-build-config.git
live-build-config/build.sh --verbose

Activities

caesarcipher

caesarcipher

2023-02-14 02:20

reporter   ~0017499

Just checking in. Is there anything else I can provide to aid with this report?

arnaudr

arnaudr

2023-02-14 05:42

manager   ~0017502

Is your git repo up-to-date? I think this issue has been fixed already.

If it's not fixed by updating the the live-build-config git repo, then it should be fixed by using the very latest versions of debian-cd and simple-cdd. Here i have simple-cdd 0.6.9 and debian-cd 3.1.36.

caesarcipher

caesarcipher

2023-02-22 17:00

reporter   ~0017550

I am able to confirm that live-builds work as expected on Debian systems again. I believe the main fix for me was to update to the newest live-build Debian package that's pulled down from the https://http.kali.org/kali/pool/main/l/live-build/ directory.

BTW, the file 'live-build_20220505_all.deb' that is specified in the directions under https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment needs to be updated to 'live-build_20230131+kali3_all.deb' on that page, but it does say you may need to double check if the files specified are the latest available, so that's probably not super urgent.

Thanks!

arnaudr

arnaudr

2023-02-23 01:38

manager   ~0017552

I updated the documentation to point to the latest file, thanks for pointing it out.

There was some work to update live-build and other related things these last two weeks. Now it's done, so everything is back to normal. Thanks for confirming that the issue is fixed for you!

Issue History

Date Modified Username Field Change
2023-01-23 21:24 caesarcipher New Issue
2023-02-14 02:20 caesarcipher Note Added: 0017499
2023-02-14 05:42 arnaudr Note Added: 0017502
2023-02-22 17:00 caesarcipher Note Added: 0017550
2023-02-23 01:38 arnaudr Note Added: 0017552
2023-02-23 01:39 arnaudr Assigned To => arnaudr
2023-02-23 01:39 arnaudr Status new => resolved
2023-02-23 01:39 arnaudr Resolution open => fixed