Package: live-build Version: 1:20190311 Followup-For: Bug #778317 Hi folks, this bug still exists. The original report talks about erronously reusing the same debootstrap cache when chaning architectures, but the problem seems broader than that. E.g. when switching distributions, you'll also get (more subtle) problems (in my case, parted from stretch refusing to install to a chroot debootstrapped as buster or sid). As stated before, (a solution to) this issue has two variants: > 1) Users can easily switch architecture in their config and then > unknowingly run into issues upon rebuilding. > 2) For users building multiple images for different architectures, while > you could just use a separate build directory for each, this would allow > using the same build directory if desired, without having to throw away > or rename the existing cached bootstrap, things would just work > automatically. Personally, I would think fixing 1) is important - preventing users from running into issues when they change config but do not erase the cache. 2) is probably more tricky to implement and seems less important. As for implementation - I guess an obvious aproach would be to keep a file inside the cache directory that indicates how this particular debootstrap cache dir was created. This should include anything that can change the debootstrap outcome, so an obvious way to do that would simply be to store the debootstrap commandline used (and also check against it when restoring the cache). This probably requires merging bootstrap_debootstrap and bootstrap_cache. Gr. Matthijs
Attachment:
signature.asc
Description: PGP signature