View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003307Kali LinuxFeature Requestspublic2016-05-23 18:572023-10-10 12:28
Reportervanguard Assigned Torhertzog  
PrioritylowSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2016.1 
Summary0003307: live-build-config request, that apt-cacher-ng can be reused again
Description

Dear maintainers,

when building a kali livefile, you request this command:

./build.sh --distribution kali-rolling --verbose

In earlier times, I could use the commands
lb config
lb build

This is working also today. When you changed the command to the first above, apt-cacher-ng worked no more, as ./build.sh purges at first the whole live-build environment.

I checked the build.sh command.

Steps To Reproduce

Do the requested command ./build.sh --distribution kali-rolling --verbose

Additional Information

I think the following changes in build.sh would make things nicer:

Line 117:
from

run_and_log $SUDO lb clean --purge <

to

run_and_log lb clean <

This does not purge the environment and apt-cacher-ng can be used again.
As you see, I left SUDO out, as not all systems use sudo (Ubuntu does, Debian not)
Same in line 135, remove SUDO.

Of course, I can edit my own ./build.sh myself, but I think, these should be the default for a fresh live-build.

Would be nice, if you agree to my suggestion!

Thank you very much!

Best

Hans

Activities

rhertzog

rhertzog

2016-05-24 07:43

administrator   ~0005273

It would help if you could explain what the requirements are to be able to use apt-cacher-ng.

On my side, I use "approx" and simply edit auto/config to make kali_mirror point to my approx setup.

I could add a new option to ./build.sh if there are specific configuration switches to pass to "lb config" (or environment variables to set).
rhertzog

rhertzog

2016-05-24 07:44

administrator   ~0005274

But I'm not going to drop "--purge", otherwise you will mix up settings from different types of images.
vanguard

vanguard

2016-05-24 08:00

reporter   ~0005275

Ok, I understand. The problem is, that I don't want to download the same packages again and again, each time I build a new version, just the updates.

The solution you told me some years ago, was to use apt-cacher-ng. This worked until the change from lb build to ./build.sh, as ./build.sh does at first a lb clean --purge. So all already downloaded packages are always deleted when I start the building and have to be dowloaded again. This is annoying.
If you have another solution, which only downloads newer versions of the packages and keep those, which are already downloaded (that what apt-cacher-ng did), then please let me know. I will be happy, to use it. Thanks
rhertzog

rhertzog

2016-05-24 08:55

administrator   ~0005276

I understand the need, but I don't understand what you have to do so that live-build download packages through apt-cacher-ng... usually you configure APT to use a proxy.

So what's wrong with ./build.sh -- --apt-http-proxy http://127.0.0.1:9999 ?
vanguard

vanguard

2016-05-24 09:09

reporter   ~0005277

There is nothing wrong with it! I just did not know, that this is existing. So I do not need apt-cacher-ng, I see. I will do as you requested. The --apt-http-proxy http://127.0.0.1:9999 must be after the "--" where my other configurationms like "keyboard=de" etc. reside?
Nice, I will do as you told, great help! I made a shell script for myself, which has the all the configurations in it.
For now, I think, you can close this bugreport/request, but please just answer my question in the close.
Thanks for the fast help. Sorry, that I have to ask such questions in the bugreporting, but I found no way, to contact one of you directly - if this is allowed.

Best

Hans
rhertzog

rhertzog

2016-05-24 09:30

administrator   ~0005278

Yes, --apt-http-proxy needs to be after "--" with other generic lb_config command line options.

You still need apt-cacher-ng or another generic proxy/cache. This option just tells live-build to use a proxy for downloads via APT and let it know where it is available (the sample I gave was for port 9999 on localhost, but other ports are commonly in use).

Issue History

Date Modified Username Field Change
2016-05-23 18:57 vanguard New Issue
2016-05-24 07:43 rhertzog Note Added: 0005273
2016-05-24 07:44 rhertzog Note Added: 0005274
2016-05-24 07:44 rhertzog Assigned To => rhertzog
2016-05-24 07:44 rhertzog Status new => feedback
2016-05-24 08:00 vanguard Note Added: 0005275
2016-05-24 08:00 vanguard Status feedback => assigned
2016-05-24 08:55 rhertzog Note Added: 0005276
2016-05-24 09:09 vanguard Note Added: 0005277
2016-05-24 09:30 rhertzog Note Added: 0005278
2016-05-24 09:30 rhertzog Assigned To rhertzog =>
2016-05-24 09:31 rhertzog Status assigned => resolved
2016-05-24 09:31 rhertzog Resolution open => no change required
2016-05-24 09:31 rhertzog Assigned To => rhertzog
2023-10-10 12:28 vanguard Status resolved => closed