Bug#1021012: linux-image-amd64 depends on linux-image-4.19.0-22-amd64, but this package is not available

Lars-Sören Steck

unread,

Sep 30, 2022, 10:40:03 AM9/30/22

to

Package: linux-image-amd64

Version: 4.19+105+deb10u17

Dear Maintainer,

The package linux-image-amd64 in the version 4.19+105+deb10u17 depends
on the package linux-image-4.19.0-22-amd64, but this package is not
available. This causes the following error, when trying to upgrade
linux-image-amd64 on a Debian Buster system:

# apt-get install linux-image-amd64
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:
linux-image-amd64 : Depends: linux-image-4.19.0-22-amd64 but it is not
installable
E: Unable to correct problems, you have held broken packages.

Thank you for your work and help.

Kind regards,

Lars-Sören Steck

Diederik de Haas

unread,

Sep 30, 2022, 1:30:03 PM9/30/22

to

On Friday, 30 September 2022 16:25:13 CEST Lars-Sören Steck wrote:
> The package linux-image-amd64 in the version 4.19+105+deb10u17 depends
> on the package linux-image-4.19.0-22-amd64, but this package is not
> available.

Likely caused by https://lists.debian.org/debian-kernel/2022/09/msg00213.html
and this issue should resolve itself when that has been corrected.

signature.asc

Bastian Blank

unread,

Oct 1, 2022, 6:30:04 AM10/1/22

to

On Sat, Oct 01, 2022 at 06:45:03AM +0000, Debian Bug Tracking System wrote:
> This will resolve itself automatically once the signed packages are
> available as well (they are in progress of beeing dealt with but needs
> a manual interaction of ftp-masters).

Looks like we need to backport the changes that moved the meta package
into linux-signed-*. This now also affects the build of the cloud
images and breaks them.

Bastian

--
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown

Ben Hutchings

unread,

Oct 1, 2022, 3:41:14 PM10/1/22

to

On Sat, 2022-10-01 at 12:23 +0200, Bastian Blank wrote:
> On Sat, Oct 01, 2022 at 06:45:03AM +0000, Debian Bug Tracking System wrote:
> > This will resolve itself automatically once the signed packages are
> > available as well (they are in progress of beeing dealt with but needs
> > a manual interaction of ftp-masters).
>
> Looks like we need to backport the changes that moved the meta package
> into linux-signed-*. This now also affects the build of the cloud
> images and breaks them.

In buster, the metapackages are still built from linux-latest. This
has a fake build-dependency on linux-headers-<version>-all to ensure it
waits for linux to be built, but it doesn't have any such relation to
linux-signed-*.

I don't think I should try to move binary packages around post-release,
so probably the best approach is to wait to upload linux-latest in
future.

(This wasn't a problem with stretch LTS because we didn't do code
signing, and it wasn't a problem with buster prior to LTS because
security updates and point releases would release all related packages
at once.)

Ben

--
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding
stump of a severed limb. - me, 29 June 1999

signature.asc

Bastian Blank

unread,

Oct 1, 2022, 4:00:04 PM10/1/22

to

On Sat, Oct 01, 2022 at 09:29:10PM +0200, Ben Hutchings wrote:
> In buster, the metapackages are still built from linux-latest. This
> has a fake build-dependency on linux-headers-<version>-all to ensure it
> waits for linux to be built, but it doesn't have any such relation to
> linux-signed-*.

Ah, damn. Forgot about that split.

Bastian

--
A Vulcan can no sooner be disloyal than he can exist without breathing.
-- Kirk, "The Menagerie", stardate 3012.4