Hello Hans,Your first mail to the mailing list is from 2025-03-03T19:26:57CET, so I have the feeling some previous history and context is missing.
On 03/03/2025 19:52, Hans wrote:
So, I rechecked. After purging everything and building again, I checked the chroot. And what did I find? A lot of entries with "trixie" in */chroot/var/lib/dpkg/info which are mostly "*.postinst" files.
That is what I would expect. The default distribution for live-build has changed to 'testing', which is currently trixie. [1]
Where are they coming from? These are all from installed packages, but all packages should be from bookworm and not trixie.
If you want to use bookworm, you should use lb config --distribution bookwormNote that if you have already run `lb config` without this option, several options will be already hardcoded 'testing', and a switch is not easily possible.
You would have to start with a clean `config` directory to fix it.
Of course I also checked sources.list in chroot, and all are "bookworm", so IMO there is no reason, why anything should contain "trixie". Bookworm does not know of trixie. Strange.....
> > I believe, THIS is the reason, why it wants to install grub-efi-amd64-
unsigned: false entries in */chroot/var/lib/dpkg/info. Question: Does the live-build script get any information from the native installed debian? Then this would explain, why it got false informations: I played with the installed native debian, just to look, which packages are new in trixie. Thus I changed my sources.list (in the native debian) temporarly to trixie (and then back). Of course my native bookworm still got the "*.postinst" files below /var/lib/dpkg/info.
The live-build script hardly depends on the native system. It uses debootstrap from the host, and (during a cross-build) qemu. That's about it. All other packages are installed inside the chroot environment, matching the distribution you have specified with `lb config`.
And if "lb build" will copy THIS to the chroot, then it will explain, what happens. However, this is just a guess. Maybe one of the live-build-maintainers knows more.
If you need further troubleshooting, could you post the content of the config directory?
With kind regards, Roland Clobus[1] https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#370
OpenPGP_signature.asc
Description: OpenPGP digital signature
