Bug#916927: aptitude: should consistently choose between signed and unsigned kernels

From	Ansgar Burchardt <ansgar@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#916927: aptitude: should consistently choose between signed and unsigned kernels
Date	2018-12-20 17:00 +0100
Message-ID	<x78TT-7BN-3@gated-at.bofh.it> (permalink)
References	<x78Ay-7uo-7@gated-at.bofh.it> <x78Ay-7uo-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

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?

Ansgar

Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#916927: aptitude: should consistently choose between signed and unsigned kernels Ansgar Burchardt <ansgar@debian.org> - 2018-12-20 17:00 +0100
  Processed: Re: aptitude: should consistently choose between  signed and unsigned kernels "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-12-20 17:00 +0100
  Bug#916927: aptitude: should consistently choose between signed and unsigned kernels Ben Hutchings <ben@decadent.org.uk> - 2018-12-20 19:10 +0100

csiph-web