Groups > linux.debian.bugs.dist > #1251703

Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10

From	Luca Boccassi <bluca@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.devel.release
Subject	Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10
Date	2025-07-03 02:00 +0200
Message-ID	<L4fwS-eP4r-1@gated-at.bofh.it> (permalink)
References	(1 earlier) <L1ZPz-dn7s-5@gated-at.bofh.it> <L1ZPA-dn7s-17@gated-at.bofh.it> <L3lO1-eevK-3@gated-at.bofh.it> <L0Tjb-cDww-1@gated-at.bofh.it> <L3lO1-eevK-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

On Mon, 30 Jun 2025 13:20:13 +0100 Luca Boccassi <bluca@debian.org>
wrote:
> Control: tags -1 -moreinfo
> 
> On Thu, 26 Jun 2025 at 19:42, Luca Boccassi <bluca@debian.org> wrote:
> >
> > On Thu, 26 Jun 2025 at 19:41, Paul Gevers <elbrus@debian.org>
wrote:
> > >
> > > [re-sending because I got the grub2 mail address wrong]
> > >
> > > Control: tags -1 moreinfo
> > >
> > > Hi,
> > >
> > > On 23-06-2025 19:29, Luca Boccassi wrote:
> > > > The latest upload of shim-signed allows alternative
dependencies on
> > > > the systemd-boot signed packages.
> > >
> > >
> > > Reading the MR related to this change [1] I got the impression
that the
> > > bookworm branch of src:grub2 needs to land in bookworm first to
prevent
> > > the risks of apt removing the bootloader. AFAICT this didn't
happen yet.
> > > What's the plan here?
> >
> > IIRC that was waiting for this:
> >
> > https://salsa.debian.org/grub-team/grub/-/merge_requests/77
> >
> > Julian and Mate still waiting on that one before uploading to
bookworm-p-u?
> 
> Julian says on Matrix:
> 
> > we don't technically need the backport in stable for testing, apt
applies the Protected: yes at a package level, and will accordingly
refuse to move grub from stable because the flag is set in the testing
one
> 
> So I believe we don't need to wait for a grub upload in order to have
> shim-signed unblocked. Thanks.

systemd-boot-installer has been pulled into testing (and into D-I RC2),
but shim-signed wasn't, despite the single unblock ticket grouping
them. So now the functionality is broken in D-I RC2. If possible, it
would be great if this was processed soon, to unbreak it, please.

Thanks!

Thread

Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-06-23 19:40 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-06-25 12:50 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Cyril Brulebois <kibi@debian.org> - 2025-06-25 13:10 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Paul Gevers <elbrus@debian.org> - 2025-06-26 20:40 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Paul Gevers <elbrus@debian.org> - 2025-06-26 20:50 +0200
    Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-06-26 20:50 +0200
      Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-06-30 14:30 +0200
        Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-07-03 02:00 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Luca Boccassi <bluca@debian.org> - 2025-07-03 19:00 +0200
  Bug#1108231: unblock: shim-signed/1.46 systemd-boot-installer/0.10 Julian Andres Klode <jak@debian.org> - 2025-07-03 19:10 +0200

csiph-web