> I think you're forgetting about Ubuntu 26.04 (LTS) that is using kernel 7.0.

Which only came out a few months ago, and which only recently released its .1, so the do-release-upgrade message only recently appeared for most people.

I'd be interested to know how many folks have changed their current production over to 26TLS in the last six months. I'm guessing not a lot.

So yes, there is a newer LTS, but what is its current market share as compared to 24 TLS (or even 22LTS)?

Ubuntu releases its LTSes in even years, and Debian does its releases in odd years:

* https://en.wikipedia.org/wiki/Debian_release_version_history...

> 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`.

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.

I believe I need to reiterate: Stable is for servers, testing is for desktops if you're not directly exposed to internet.

Again. Stable is for servers, testing is for personal use.

I never argued otherwise, ever.

Google disagrees - https://itsfoss.com/goobuntu-glinux-google/

The comment you're replying to makes clear that they're not using it on servers. I do the same thing (testing on my laptop(s), stable on my servers); you just have to commit to keeping track of what's going on and manually patch if you think that it's necessary.

I have to add that for me, testing definitely breaks stuff sometimes. Nothing beyond my ability to fix, though. Nothing beyond anyone's ability now that AI is around.

Times are changing! Remember when it was easy to set up WiFi, but difficult to call your doctor and get an appointment?

Now my friends don't have trouble calling doctors, but can't set up port forwarding (not like any games require it anymore).

I just wanted a human recommendation; don't trust the LLMs at all.

Thanks for the link (above).

While I have your attention, can you constrast this human comment with your [presumably] human-derived username?

–ProbablyNotMachines