On Mon 03 Mar 2025 at 22:24:57 (+0100), 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. > > Where are they coming from? These are all from installed packages, but all > packages should be from bookworm and not trixie. > > 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
Yes, but what did you do while that sources.list was in place? > (and then back). What were the actual steps you took to restore your native debian to bookworm? Those three parenthesised words impart close to zero information. > Of course my native bookworm still got the > "*.postinst" files below /var/lib/dpkg/info. ‘the’ *.postinst files: which ones specifically. Your saying "of course" doesn't seem to carry much weight any more. > And if "lb build" will copy THIS to the chroot, then it will explain, what > happens. However, this is just a guess. You see? If that is /the/ explanation for your build problem, then you're implying here that your native system is now a frankendebian, aren't you? > Maybe one of the live-build-maintainers knows more. Probably they do, but I wouldn't think they'd want to get involved in your problem, when you've already accused them of being the cause of it at the start of the thread. Cheers, David.
