Reintroduce regular building of live-build images

Build the bookworm images on a regular basis again.

The script is based on old/run-30live-build and the script that currently runs in Jenkins

added 15 commits

• c10d4850...5c694040 - 10 commits from branch images-team:master
• 73796af8 - Allow the scripts to be run from any git checkout folder
• e14a6a60 - Remove the 'running' flag file
• d23c9626 - Use 'run_log'
• 689fb4e2 - Create directories where needed
• cfdd5729 - Add target 'smallest-build' for quicker tests

Compare with previous version

marked this merge request as draft

Some updates. I've not pushed the hacks that I needed to configure the VM locally.

For testing use 'smallest-build', which does not contain d-i or additional packages. If needed, that specific commit can be excluded from the cherry-picking

I've successfully generated a 'smallest-build' image (which does not contain d-i), but not yet 'standard' (the next bigger one in size).

I'm using a bullseye VM, but the installer part of the live-builder script needs some information about bookworm, which it not part of the (older) live-build package. I haven't encountered this before, because I always used testing (bookworm) while working on the scripts for live-build.

I'll build a testing-based VM next, to see whether that would make it possible to generate all images.

resolved all threads

added 3 commits

• 8c39e9df - live-build-binary needs the codename
• 7541725b - Reflect the new name of the vm-start script
• 160cfa27 - Use ISO-8601 timestamps

Compare with previous version

added 2 commits

• 09fc50fc - Documentation: CONF.sh
• ca60934b - Rebuild the image when the archive was updated while building

Compare with previous version

On my local machine I've been able to generate 'smallest-build', 'standard' and 'gnome', all using a testing-based VM.

When the archive gets updated while the image is being built, it builds the image again, to ensure that the image is reproducible. The images are reproducible within the same DAK-sync-run. I'll try to find a way to ensure long-term reproducibility without the need for a snapshot server.

The commands that I've used:

bin/vm-start -a amd64 -t live -r bookworm -o vm_config
bin/run-live-build-binary -B BL_amd64_standard -r bookworm -c vm_config -l mylog
bin/run-live-build-binary -B BL_amd64_gnome -r bookworm -c vm_config -l mylog
bin/vm-stop -c vm_config

Open questions:

• Does it make sense to try to use a bullseye or buster VM-image?
• The documentation mentions a Makefile. Is that file stored in some other repository?
• The live-build-binary script contains some variables that currently are not used: VOLID, DESCRIPTION. I'll see whether they (in some form) can be passed along to the rebuild script.

In short: I think the scripts as they currently are, are sufficient to get the first rounds of regular live images activated again.

marked this merge request as ready

added 1 commit

• 0297d19e - live-build: Unmodified rebuild script

Compare with previous version

mentioned in commit 113c09ae

merged