Your message dated Mon, 2 Sep 2019 11:31:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#939160: grub-efi-amd64-signed: not installable, broken
dependencies
has caused the Debian Bug report #939160,
regarding grub-efi-amd64-signed: not installable, broken dependencies
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
939160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939160
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub-efi-amd64-signed
Version: 1+2.04+2
Severity: grave
Justification: renders package unusable
Hi!
While trying to enable Secure Boot on my laptop installing mandatory
packages, I faced this:
$ sudo apt install grub-efi-amd64-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
grub-efi-amd64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is to be
installed
E: Unable to correct problems, you have held broken packages.
Thanks for the efforts spent fixing it.
Cheers.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages grub-efi-amd64-signed depends on:
ii grub-common 2.04-3
Versions of packages grub-efi-amd64-signed recommends:
ii shim-signed 1.33+15+1533136590.3beb971-7
grub-efi-amd64-signed suggests no packages.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sun, Sep 01, 2019 at 08:28:20PM +0200, Matteo F. Vescovi wrote:
> While trying to enable Secure Boot on my laptop installing mandatory
> packages, I faced this:
>
> $ sudo apt install grub-efi-amd64-signed
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> grub-efi-amd64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
You're using unstable, which isn't guaranteed to stay
dependency-consistent. The way that the signed GRUB packages work means
that there'll always be a short window after a grub2 upload to unstable
when the corresponding signed packages aren't available yet, and you ran
into that window.
grub-efi-amd64-signed should be installable again now in unstable; but
if you want to avoid ever running into this problem, you'd be better off
running testing.
Cheers,
--
Colin Watson [[email protected]]
--- End Message ---
