undefined

points

[-]

That, or just pick the kernel package from unstable or testing. Apt is smart enough that mixing packages from different versions of Debian works just fine.

(I mean nothing is 100% but I've been mixing packages for like 2 decades now and literally can't remember any specific trouble resulting from it.)

by so-rose2 hours ago|

parent|

[-]

> That, or just pick the kernel package from unstable or testing. Apt is smart enough that mixing packages from different versions of Debian works just fine.

While I won't deny that this may often work, I disagree that it's a good idea, and that `apt` being smart is sufficient to guarantee that this works (or keeps working in the future).

Pinning specific packages from `testing` or `unstable` is explicitly discouraged, for very good reasons covered by this classic link: https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank... .

Arguably, the backports kernel is the right choice to get a newer kernel on Debian Stable. Indeed, in the past, the backports kernel could take awhile to update, but no more - case in point, `trixie-backports` currently contains `7.2`, same as `unstable`.

by Dylan1680756 minutes ago|

parent|

[-]

I'd be wary of mixing software packages from different releases because their libraries might interact weirdly. But the kernel should be more isolated. Not isolated enough?

Either way backports does sound like the best option, sure.

by seba_dos13 hours ago|

parent|

prev|

[-]

It's not apt not being smart that can cause troubles when mixing packages from various suites. There's no reason to mix in cases where you can just use backports instead.