Good idea, Matthias, so I rechecked. There are only two packages in packages.chroot in the last build I sent the output from.
These were "kali-undercover_2023" and "rustdesk-1.3.7". In both I checked the "control" file, but none of them pointed to or named "grub-efi-amd64-*". But to clear things, I am rebuilding again without these two packages. Please mote, I added several packages in my own list below "package-lists", but in my list only packages from the debian repo are liisted. If one of these recommends grub-efi*-unsigned, then it is a package problem, but I am quite sure, this is not the cause of the issue. Oh, and to make sure, there are no remains from somewhere, any build is been started with the "lb clean --purge" command. One thing, I could not discover yet: My first live-build tree is rather old, and I could not find a way, to upgrade it, but also did not want to delete everything. I tried git pull origin master but this did not work. I suppose, the command is false? Maybe you could drop me a hint, how to upgrade it, so I will try again. Hans > Hans, let me reiterate this: Maybe you had put another package from > trixie/testing into packages.chroot, which depends directly or > indirectly on grub-efi-amd64-unsigned? > Possible packages in testing/trixie main are: > - grub-efi-amd64-bin depends on grub-efi-amd64-unsigned > - grub-efi-amd64 depends on grub-efi-amd64-bin > - shim-signed depends on grub-efi-amd64-bin > > And debian-l...@lists.debian.org could be a good starting point for > your problem. > > Best regards. > Matthias
