Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
On 1/22/25 22:32, Michael Stone wrote:
I think the problem here is a misunderstanding of how backports work:
they're not "the latest kernel", they're "the latest kernel from debian
testing". You're not going to see a kernel in backports that's not going
to be in trixie until after the trixie release. (And even then it would
be going into trixie-backports, not bookworm-backports.) Simply install
linux-image-amd64 from bookworm-backports and you'll be fine.
You mean, linux-image-amd64 in bookworm-backports, which currently draws
in linux-image-6.12.9+bpo-amd64 (= 6.12.9-1~bpo12+1), can be expected
to NOT draw in some 6.13 like 6.13~rc7+1~exp1 currently already having
appeared in the experimental repository, because that 6.13 is not
expected to make it into current testing (Trixie) no more?
Then this linux-image-amd64 from backports would indeed be perfectly
fine to install to my Bookworm! Problem solved!
Correct?
Reply to:
- References:
- Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: Marco Möller <talby@debianlists.mobilxpress.net>
- Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: George at Clug <Clug@goproject.info>
- Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: Marco Möller <talby@debianlists.mobilxpress.net>
- Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: Greg Wooledge <greg@wooledge.org>
- Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: Marco Möller <talby@debianlists.mobilxpress.net>
- Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13
- From: Michael Stone <mstone@debian.org>