View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003283Kali LinuxKali Package Bugpublic2016-05-09 07:282025-07-14 09:37
Reportervanguard Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version2016.1 
Summary0003283: kali-git points to sana, but should point to kali-rolling
Description

Dear kali-team,

I am regularly building a kali-livefile for my purposes. I discovered, that a fresh live-build environment for kali is based and pointing to "sana". As the official release is "kali-rolling" all defaults should point there.

Maybe this is the reson for some trouble I am in.

First, every kali-livesystem crashes at boot (please see bug 0003274)

Second:I am building with German environment. As in LXDE everything is in German, the other terminals are in English. To switch to German with "loadkeys de" does not work! All necessary packages are installed. Please see bug 0002108 and 0002727

Steps To Reproduce

Building kali-linux in several ways with the samen results. Please see bug 0003274 for further informations.

Additional Information

I would like to send more information, but due to bug 0003274 I cannot test any builds as they all crash at boot. Thus it is impossible for me, to try different configurations to fix the German language bugs.

Please ask for more information or hints about the build.

Best regards

Hans

Activities

rhertzog

rhertzog

2016-05-09 08:20

administrator   ~0005201

I'm sorry but this is just not true. Are you sure that you have the latest version on what's in live-build-config git repository?
vanguard

vanguard

2016-05-09 08:36

reporter   ~0005202

Ok. let's guess I am wrong.

I did so:
git clone git://git.kali.org/live-build-config.git

then
lb config (I have to do this at first, so that I get the config-directoriies, which then I can ediit to my needs, if wished)

Now take a look at:

~/live-build-config/binary
~/live-build-config/bootstrap
~/live-build-config/builld
~/live-build-config/config/auto

All point to sana. The --distribution kali-rolling directive does not change all entries to kali-rolling.

However, I may think still false!

Best regards

Hans
rhertzog

rhertzog

2016-05-09 10:42

administrator   ~0005215

Ok. The default in ./build.sh is correct but the default in auto/config was wrong. Since I never used lb config directly but only through ./build.sh I did not notice it.

It's now fixed.
vanguard

vanguard

2016-05-09 11:59

reporter   ~0005217

Hi Raphael,
thanks for your fast reaction. Sadly it is still not fixed, as now there is a new error.
Please see:

~/tmp$ git clone git://git.kali.org/live-build-config.git
Klone nach 'live-build-config' ...
remote: Counting objects: 974, done.
remote: Compressing objects: 100% (679/679), done.
remote: Total 974 (delta 522), reused 426 (delta 220)
Empfange Objekte: 100% (974/974), 832.84 KiB | 558.00 KiB/s, Fertig.
Löse Unterschiede auf: 100% (522/522), Fertig.
Prüfe Konnektivität ... Fertig.
~/tmp$ cd live-build-config/
~/tmp/live-build-config$ lb config
[2016-05-09 13:55:48] lb config
P: Executing auto/config script.
ERROR: Run this first:
ln -sf sid /usr/share/live/build/data/debian-cd/kali-rolling
rhertzog

rhertzog

2016-05-09 12:14

administrator   ~0005220

If you persist in using "lb config" manually, you should at least learn to figure out problems by yourself... if you run "./build.sh" it will complain of the fact that you don't have the correct version of live-build.

The Kali version of live-build is patched and contains the expected symlink that seems to be missing (/usr/share/live/build/data/debian-cd/kali-rolling).

So please stop reopening ticket without having investigated issues a bit more thoroughly. Thank you.

Issue History

Date Modified Username Field Change
2016-05-09 07:28 vanguard New Issue
2016-05-09 08:20 rhertzog Note Added: 0005201
2016-05-09 08:36 vanguard Note Added: 0005202
2016-05-09 10:42 rhertzog Note Added: 0005215
2016-05-09 10:42 rhertzog Status new => resolved
2016-05-09 10:42 rhertzog Resolution open => fixed
2016-05-09 10:42 rhertzog Assigned To => rhertzog
2016-05-09 11:59 vanguard Note Added: 0005217
2016-05-09 11:59 vanguard Status resolved => feedback
2016-05-09 11:59 vanguard Resolution fixed => reopened
2016-05-09 12:14 rhertzog Note Added: 0005220
2016-05-09 12:14 rhertzog Status feedback => closed
2016-05-09 12:14 rhertzog Resolution reopened => fixed
2025-07-14 09:36 g0tmi1k Priority high => normal
2025-07-14 09:37 g0tmi1k Severity block => minor