On Wed, 28 Jan 2026 10:53:49 +0000 Adam D. Barratt wrote: > On Wed, 2026-01-28 at 01:50 +0100, Vincent Lefevre wrote: > > On 2026-01-28 00:47:23 +0100, Francesco Poli wrote: > > > I am retrying now, but I cannot reproduce the issue anymore. > > > Just a calmer time, or has anything been fixed on fastly? > > > > On a bookworm machine, I got the following error several times > > about one hour ago: [...] > > That should work now.
The situation looks definitely improved, although I was seeing the
following about one hour ago:
$ apt-listbugs list grub-efi-amd64
Retrieving bug reports... 0% Fail
E: HTTP GET failed (503: Backend fetch failed)
Retry downloading bug information? [Y/n]
One package at a time? [Y/n] n
One bug report at a time? [Y/n] n
Fail
E: HTTP GET failed (503: Backend fetch failed)
Retry downloading bug information? [Y/n]
One package at a time? [Y/n] n
One bug report at a time? [Y/n] n
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of grub-efi-amd64 (→ ) <Outstanding>
b1 - #1102160 - upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs
unpacking failed invalid magic at start of compressed archive
b2 - #913576 - Update to grub-efi-amd64 2.02~beta3-5 results in "error:
efibootmgr failed to register the boot entry: Operation not permitted."
b3 - #913916 - grub-efi-amd64: UEFI boot option removed after update to
grub2 2.02~beta3-5+deb9u1
b4 - #984520 - 'error: symbol "grub_register_command_lockdown" not found'
and then lightdm fails to start
Summary:
grub-efi-amd64(4 bugs)
But now, I am not seeing any errors:
$ apt-listbugs list grub-efi-amd64
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of grub-efi-amd64 (→ ) <Outstanding>
b1 - #1102160 - upgrade-reports: Bookworm to Trixie [amd64][EFI] initramfs
unpacking failed invalid magic at start of compressed archive
b2 - #913576 - Update to grub-efi-amd64 2.02~beta3-5 results in "error:
efibootmgr failed to register the boot entry: Operation not permitted."
b3 - #913916 - grub-efi-amd64: UEFI boot option removed after update to
grub2 2.02~beta3-5+deb9u1
b4 - #984520 - 'error: symbol "grub_register_command_lockdown" not found'
and then lightdm fails to start
Summary:
grub-efi-amd64(4 bugs)
>
> > But I'm wondering why apt-listbugs uses port 80.
>
> It appears that up to (and including) bookworm, TLS support was
> resisted due to concerns around OpenSSL licensing. From trixie onwards
> HTTPS is used.
Exactly.
>
> Regards,
Bye Adam, and thanks to you and to the other involved people for
fixing/improving the situation!
Your time and dedication is much appreciated.
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpCLx414oXDy.pgp
Description: PGP signature
