[Aptitude-devel] Bug#916927: aptitude: should consistently choose between signed and unsigned kernels

Ansgar Burchardt ansgar at debian.org
Thu Dec 20 15:51:47 GMT 2018

Control: reassign -1 src:linux 4.19.9-1

On Thu, 20 Dec 2018 16:26:55 +0100 Vincent Lefevre wrote:
> After an upgrade of linux-image-amd64, which now depends on
> linux-image-4.19.0-1-amd64, on one machine I got:
>   linux-image-4.19.0-1-amd64 4.19.9-1
> but on another machine I got:
>   linux-image-4.19.0-1-amd64-unsigned 4.19.9-1

The issue is that linux-image-4.19.0-1-amd64-unsigned has
  Provides: linux-image-4.19.0-1-amd64

So if linux-image-amd64 starts depending on linux-image-4.19.0-1-amd64
before the signed version is present, apt will install the unsigned
version.  This doesn't look like a bug in apt to me.

The easiest way to avoid this would be to drop the Provides from the
unsigned image.  Is there any downside for doing so?


More information about the Aptitude-devel mailing list