Hi Carsten, hi Leandro,
I was misleading. Not the package name of linux-image-amd64 is changing, but the package name of the supported stable kernel (currently linux-image-4.19.0-16-amd64).
When there is a new stable kernel it will be installed as a dependency of an updated linux-image-amd64.
I could either install linux-image-amd64 from buster (currently 4.19+105+deb10u11) to always get the current stable kernel, or install/update it from buster-backports (currently 5.10.24-1~bpo10+1).
In the latter case my setup would not pull linux-image-4.19.0-17-amd64 or later, in the former case it would not pull the latest backports kernel, automatically on upgrade.
Did I overlook a possibility to install linux-image-amd64 from stable AND backports to follow both lines at the same time?
Btw the motivation behind this is, for some time I had problems with the backports kernel in a specific setup and it was convenient to just boot the current stable kernel as a backfall solution.
Thanks in advance
Johan
Hello Johannes,
Am 08.06.21 um 08:37 schrieb Johan Kröckel:
> Hi, thanks for the answer but not a solution in this situation. The
> result would be no up to date stable kernel installed when the package
> name changes.
the trick is that the name 'linux-image-amd64' isn't changing over time.
This particular package is a virtual package which is depending on some
the real kernel package for a specific version. This is e.g. for the
current package in testing.
> $ apt-cache show linux-image-amd64
> Package: linux-image-amd64
> Source: linux-signed-amd64 (5.10.40+1)
> Version: 5.10.40-1
> Installed-Size: 13
> Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
> Architecture: amd64
> Provides: linux-image-generic, linux-latest-modules-5.10.0-7-amd64, virtualbox-guest-modules, wireguard-modules (= 1.0.0)
> Depends: linux-image-5.10.0-7-amd64 (= 5.10.40-1)
> Description-en: Linux for 64-bit PCs (meta-package)
> This package depends on the latest Linux kernel and modules for use on PCs
> with AMD64, Intel 64 or VIA Nano processors.
> Description-md5: 6a25122b463a5515998ee600e16b3daf
> Homepage: https://www.kernel.org/
> Built-Using: linux (= 5.10.40-1)
> Tag: admin::kernel, role::metapackage
> Section: kernel
> Priority: optional
> Filename: pool/main/l/linux-signed-amd64/linux-image-amd64_5.10.40-1_amd64.deb
> Size: 1480
> MD5sum: 4401615b6b06321b89d483ede3d74aa8
> SHA256: 19037cbb57febff59b480ee947980eff91666e3fe4a1be0736f2e5c3c92b3d63
As long as you use 'linux-image-amd64' you will get the latest supported
kernel version. But you will need this both times, once for the stable
release and once for the buster-backport release, if you want both
kernel versions get installed.
> $ rmadison linux-image-amd64
> linux-image-amd64 | 3.16+63+deb8u2 | oldoldstable | amd64, i386
> linux-image-amd64 | 4.9+80+deb9u11 | oldstable | amd64
> linux-image-amd64 | 4.19+105+deb10u4~bpo9+1 | stretch-backports | amd64
> linux-image-amd64 | 4.19+105+deb10u11 | stable | amd64
> linux-image-amd64 | 5.10.24-1~bpo10+1 | buster-backports | amd64
> linux-image-amd64 | 5.10.40-1 | testing | amd64
> linux-image-amd64 | 5.10.40-1 | unstable | amd64
--
Regards
Carsten