Re: Nearly reproducible Bookworm 12.6 live images

Philip Hands <[email protected]> Wed, 03 Jul 2024 21:31:14 +0200

Newsgroups	gmane.linux.debian.devel.cd
Message-ID	<[email protected]>

Roland Clobus <[email protected]> writes:

> Hello lists,
>
> I'm sooo close...
>
> Now that that 12.6 live images have been generated [1], there is only 
> one embedded timestamp left (/boot/grub/live-theme/theme.txt and its 
> parent folder)
> I've not seen this timestamp issue before, as I am using a slightly 
> different way of building the image than live-setup uses.
>
> live-setup uses a local cache of the git repository of live-build, to 
> avoid being blocklisted by salsa for heavy traffic, caused by parallel 
> builds.
> This local cache brings that this file could have an old timestamp, 
> whereas my local builds always used 'now' (caused by git clone), which 
> would be properly truncated to SOURCE_DATE_EPOCH, and therefore be 
> reproducible.

AFAIK it's the repeated full clones that get you blocklisted.

I was having the same issue with the openQA workers which I've fixed by
adding a --reference-if-able option pointing at a locally accessible
copy of the repo on the workers (in fact the "local" copy is an nfs
mount, but it's enough to ensure that the worker is not trying to do a
full clone from salsa, and so avoids the blocklist)

I guess the thing to do is a fetch against the cache repo first just to
make sure it stays updated, then a clone while pointing at that repo
via the --reference-if-able option, then it'll still give you the same
result as doing a clone, without overloading salsa.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

signature.asc (application/pgp-signature, 832 B)