wicd is unlikely to come back because it depends on a python2 package (pygtk which is no longer maintained upstream) - wicd isn't something we modified for Kali use, so it's not something we can easily bring back since it has been removed from Debian testing - https://tracker.debian.org/pkg/wicd - there are python3 forks of it, e.g. https://github.com/PXke/wicd-reloaded but that isn't packaged anywhere, as far as I know. Since we pull from Debian testing, when it was removed there, it was removed here as well (and the missing dependency means it won't install)

Can you provide the full output of the build with sa-compile crashing?

kali/kali should be the correct login credentials, the only time it should be different is an actual installation where the user creates their username and password.

And you are correct for the git url, it is a holdover from when our repositories were hosted on github.

Hi,
thanks for the quick answer. For wicd I will find a similar tool, which is as easy to use as wicd. Maybe network-manager might be my choice.

kali/kali does not work, rechecked. Maybe this is a problem in your configuration files of git used by live-build. Would be nice if you could recheck this.

Withthe git-problem, maybe you might want to enter a uniique entry on your site, so that it is telling the same correct thing in your documentation.. Just a suggestion.

And last but not least, for sa-compile I uploaded my build.log, hope it will be usefull.

Thank you very much for your help.

Setting up sa-compile (3.4.4-1) ...
Running sa-compile (may take a long time)
chmod: cannot access '/var/lib/spamassassin/compiled': No such file or directory
dpkg: error processing package sa-compile (--configure):
installed sa-compile package post-installation script subprocess returned error exit status 1

So it looks like the post-install is trying to chmod the directory that doesn't exist because there are no spam assassin rules to convert (I'm just guessing based on the package without looking closer) - this is a Debian package, not one that we modify, so it's probably better to submit an issue to the Debian bug tracker.

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://kali.training/topic/filing-a-good-bug-report/