Dear maintainers,

it is no more possible to build debian-live/stable (bookworm). The reason is a missing package in bookworm: grub-efi-amd64-unsigned.

I rechecked and yes, it is no more in bookworm. Of course, I could download it as single package and put it in packages.chroot, but there are a lot of dependencies, which are also have to be put into and this makes it
complicated.

I believe a better way is, to change the configuration on the master server,
so that this package is no more needed. Maybe exchange it to grub-efi-amd64- signed?

As a workaround (and trixie is already in sight), I changed the settings to trixie, which is building like a charm.

Thank you for reading this.

Best regards

Hans

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am Sonntag, 2. März 2025, 13:37:20 CET schrieb Matthias Böttcher:

PS.

Hans, maybe you put another package from trixie/testing into
packages.chroot, which depends directly or indirectly on grub-efi-amd64-unsigned?

Hi Mathias,

I already had this idea, too, but putting it from testing will force to add lots of other packages from testing, too. This is a lot of work and a big chance, to make mistakes.

So my idea was just to write to the live-file-maintainers, to ask them, to remove the dependency of the missing package in theire configurations or point it to another package, i.E. grub-efi-amd64-signed.

I tried also, to change any enty of "bookworm" to "trixie" in */live-build- config/binary, */bootstrap */chroot, */common and */source, so that my livebuild will be trixie. Did not work due to another dependency failure.

(I am using debian-live as base for some projects of mine (Rustdesk-live, Elasticsearch-live and my special made Debian-live with my own package lists for teaching purposes.)

But please do not hurry! Trixie is in sight, so debian/stable might become unimportant soon.

Have a nice day!

Hans

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun 02 Mar 2025 at 17:44:37 (+0100), Hans wrote:

So my idea was just to write to the live-file-maintainers, to ask them, to remove the dependency of the missing package in theire configurations or point
it to another package, i.E. grub-efi-amd64-signed.

Presumably you meant "remove the dependency /on/ the missing
package". Can you help us by /naming/ the package that depends
on grub-efi-amd64-unsigned.

Cheers,
David.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi David,

yes, that is, what I meant.
But now, I am a litle bit lsot. How shall I get, which package depends grub- efi-amd64-unsigned? I thought, you might know.

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".

Any idea, how to get it? I am not sure, but I would estimate, it is grub- common, but maybe an older one?

The package grub-efi-amd64-unsigned is disappeared from debian/stable, but I
do not know, which package recommended it.

Sorry, I can not help further on at the moment, but I will go on researching.

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.

I thought, the developers of debian-live does it much better know than me!

Please excuse, I am not able to give any more information at the moment.

Best

Hans

Presumably you meant "remove the dependency /on/ the missing
package". Can you help us by /naming/ the package that depends
on grub-efi-amd64-unsigned.

Cheers,
David.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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-live@lists.debian.org could be a good starting point for
your problem.

Best regards.
Matthias

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

So, tried agian without the */packages-lists/mylist.list.chroot and without
any added packages at */packages.chroot = same issue again.

This excludes the cause by any changes from me or by any added packages.

It is proven, the issue is in the live-build environment itself.

Hans

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)