Hi vanguard!

It's a bit strange, this particular issue was fixed one or two weeks ago already. We didn't see this error message since then, and our daily builds succeed. I just tried to build a live image on my machine (amd64 host) and it succeeds. Are you sure that everything is up to date on your side? Can you post the complete logs (including the exact command that you run), maybe I'll understand better what can go wrong?

Hi arnaudr,

it looks like the error is now gone. Today I tried again, this is what I did.
But please let this bugreport open for a few days more, as I want to be surem if the bug is really gone.
I am building for i386 (using on my EEEPC) and for amd64 (which is also building environment), but as my computers are not very fast, this is lasting
for hours each.

Step-by-step:

Preparations:

1. I am building using the latest kali live I build myself.

2. I deleted the whole directory "live-build-config" to get rid of old configurations, then created a new one with the command from the
   kali website "git clone https://gitlab.com/kalilinux/build-scripts/live-build-config.git"

3. THIS IS IMPORTANT(!): changed into live-build-config and in this directory doing the command "lb config". For the first time this is necessary. It is creating the whole build tree (and missimng directory and configs), so you are able to change configs also before the very first build, as needed. Off topic: Maybe this should be added in the documentation of the kali site!

4. I copied my own file list into ~/live-build-config/config/package-lists

5. Last I copied some additional packages, which are not available (like jnetmap, rlinux or eeepc-acpi-scripts) into ~/live-build-config/config/package-chroot/

The Build:

1. For easy build, and so that I do not always have to download every package again, I am using apt-cacher-ng and two self created shell scripts (see attachement). The first is called "uit-update.sh", which is setting my environment (I am mounting a SSD below /mnt), installs needed packages in the live system, automatically updating the git tree, copies the acng.conf to the right place and starts apt-cacher-ng again.

2. Next I start "uit-build.sh" with the correct variable set for i386 (in this example I am building for i386, but amd64 is tunning into the same issue), environment for apt-cacher-ng, bootappends and so on. Look into the attached script, it does everything explain.

This always worked, with the only problem, that the new created live system is always starting XFCE automatically, but should start LXDE, but this issue was opened in another bugreport.

Hope, this makes things a little clearer and also helps other people.

I do not know, if there are people in the worls, which are building kali-live with similar thoughts like me, I believe, most people are building stock live kali systems with no changes, in English, no packages added, no change of environments. Doing so, of course, is well tested with nightly builds.

Thank you very much for your help.

Best regards

Hans

#!/bin/sh
### Author Hans-J. Ullrich <[email protected]>
### License: GPL

### Set some variables, not active yet.
### architecture: i386, amd64, arm
ARCH=i386
### Distribution, you might not want to change it.
DISTRO=kali-rolling
### Your preferred window-manager: lxde, kde, xfce, gnome
VARIANT=lxde
### Environmet for your local proxy
PROXY=http://localhost:3142/
### language, keyboard, locales everything you might not need to change
BOOTAPP="boot=live hostname=uit-kali ignore_uuid locales=de_DE.UTF-8 keyboard-layouts=de keyboard-variants=nodeadkeys"

### Clean your system, not really necessarey, as the latter "./build.sh" does 
### this either.
# lb clean

### VERY IMPORTANT: Make sure, apt-cacher is started, even, if you are sure, 
### it is already running!
/etc/init.d/apt-cacher-ng stop && sleep 3 && /etc/init.d/apt-cacher-ng start

### set your needed environment and preparations.
export http_proxy=http://localhost:3142/
lb config 

### This command starts the actual build. All commands are in one line. 
### However, this script might be improved, to use variables for better 
### configuration possibilities.
# ./build.sh --arch $ARCH --distribution $DISTRO --variant $VARIANT --verbose -- --apt-http-proxy $PROXY
./build.sh --arch $ARCH --distribution $DISTRO --variant $VARIANT --verbose -- --apt-http-proxy $PROXY --bootappend-live "$BOOTAPP"

### these options can be used for further commands after build
### for example, if you want to burn a dvd, shutdown, whatever
### Examples for my personal needs below
#/etc/init.d/apt-cacher-ng stop

### Suggestions for handling the built image.
# cp /home/username/live-build-config/images/*.iso /home/user/
# wodim /path_to_your_live_build/live-build-config/images/your_image_name.iso

### Some opportunities at unattended build run, what to do after the build succeeded.
# halt -p
# reboot
# shutdown -h now

#!/bin/sh


### define path to the repository on your disk
### PATH=
MOUNTPOINT=/mnt
# DEVICE=/dev/sdb1
REPOPATH=kali-linux/var/cache/apt-cacher-ng/

###  download and install needed packages
apt-get update
apt-get install git cdebootstrap live-build live-config apt-cacher-ng console-data curl -y

### execute any commands to fit your personal environment
loadkeys de

### prepare youre proxy and make sure, your local repo has ownership "apt-cacher-ng:apt-cacher-ng"
cp acng.conf /etc/apt-cacher-ng/
chown -R apt-cacher-ng:apt-cacher-ng $MOUNTPOINT/$REPOPATH

### updating the git branch
git pull origin master

### This is a test szenario, execute other scripts as needed
### This suggestion calls my very own script.
# ./uit-build-i386.sh

This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/