Bug#1067486: Depends: grub-common (= 2.12-1) but it is not going to be installed

[Eduard Bloch]

reopen 1067486
reassign 1067486 apt
severity 1067486 normal
thanks

Am Fri, Mar 22, 2024 at 11:46:02PM +0100 schrieb Julian Andres Klode:

> > Please upload a new version so grub-efi-amd64-signed can be installable.
> > Thanks!
> 
> I'm getting a bit tired of this. This is normal, the packages are
> automatically generated but need to be approved by ftpteam. 

This might be a normal condition but a) this is not transparent to user,
and b) it really does break apt's operation, at least partly.

For a) maybe we should make this somehow auto-checked remotely and shown
in reportbug? Or would you have a better idea?

And for b) all "dist-upgrade" or "full-upgrade" failed suddenly. Yes,
failing, user getting completely locked out. And "upgrade" operation
installed just a fraction of the potential candidates (there were more
reasons for that but the lack of dist-upgrade feature is still PITA).
And the reason has not been obvious, and even debugging with
-oDebug::pkgProblemResolver=true is NO FUN on bigger upgrades.

And the eventual solution was close examination, and some
guessing/observing that apt is confused and jumps between amd64 and
i386, and then some FORCE magic, i.e.

dpkg --remove --force-depends grub-common:i386

(don't ask me how this package got installed before, that system
installation has been migrated a lot). Another candidate was an old
iproute:i386 package which I also had to remove.

Best regards,
Eduard.