On 2025-03-03 David Wright wrote:
> On Sun 02 Mar 2025 at 20:32:24 (+0100), Hans wrote:
>
> > The only thing I got, was the message from "lb build", that a ncessary
> > package
> > could not be downloaded. And the necessary package was named
> > "grub-efi-amd64-
> > unsigned".
>
> That suggests to me (with no experience of this) that its a script
> that's asking for it, not a package dependency.
>
> > One of the packages debian-live wants to install must have this dependency,
> > but I am also not knowing, which packages debian-live wants to install.
> So (again, with no experience of this) I can only guess that you've
> intentionally or unintentionally selected an option for your build
> that wants to download grub-efi-amd64-unsigned.
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
