Hi Julian, Thank you for the reply.
The failure I encountered was an unbootable system; see `/var/log/apt/history.log` below. In that configuration, the system reboots at the grub loading screen, instead of proceeding to the grub menu. I was able to use Super Grub Disk to log in, downgrade and restore the missing packages, but I think this behavior qualifies as "critical." I would appreciate any assistance you can provide forwarding this report to the correct team. ``` Start-Date: 2024-03-13 12:21:38 Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 56623118 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpabiw_6dz Requested-By: me (1000) Upgrade: grub-firmware-qemu:amd64 (2.06-13+deb12u1, 2.12-1~bpo12+1), grub2-common:amd64 (2.06-13+deb12u1, 2.12-1~bpo12+1), grub-common:amd64 (2.06-13+deb12u1, 2.12-1~bpo12+1) Remove: grub-efi-amd64:amd64 (2.06-13+deb12u1), grub-efi-amd64-bin:amd64 (2.06-13+deb12u1), shim-signed:amd64 (1.39+15.7-1) End-Date: 2024-03-13 12:21:45 ``` On Wed, 20 Mar 2024 12:39:02 +0100 Julian Andres Klode < julian.kl...@canonical.com> wrote: > On Fri, Mar 15, 2024 at 08:56:25PM -0400, TM wrote: > > Package: grub-efi-amd64-bin > > > > Version: 2.12-1~bpo12+1 > > > > Hello, > > > > This package seems to require[1] grub-efi-amd64-signed >= 1+2.12, which is > > available in testing[2]. > > > > Please excuse the report if this is expected behavior. Apt output follows. > > > > Thank you for your time. > > > > We did not upload that backport, and this is normal and expected > behavior, and it's out of our hands and up to the ftp team to approve > the signing binaries - it's not a bug. > -- > debian developer - deb.li/jak | jak-linux.org - free software dev > ubuntu core developer i speak de, en > >