- cross-posted to:
- debian@lemmy.ml
- cross-posted to:
- debian@lemmy.ml
Looking at Debian’s release-critical bugs, you can see that Trixie is close:
Testing now has fewer critical bugs than Stable, and the number is dropping quickly.
About 200 bugs still need to be fixed to get the number down to where the previous releases were done.
Maybe you can help? Bugs blocking the next release can be as simple as missing translations for the upgrade instructions.
It’s been reported (Debian mailing list, Phoronix, Linuxiac) that Debian 13 will likely be out this summer. The hard freeze is on May 15 and usually that means the actual release is pretty close, just a couple of months away.
Phoronix speculated that, since Debian 12 went from initial freeze to stable release in 5 months, Debian 13 could release around August.
Pleeaaasssee get kernel 6.14 in, or at least to Backports. I’ve been doing work to support the new dual screen Zenbook Pro in Linux, and I’m having to do it with Ubuntu 25.10 because Backports only goes to 6.13. Though my trusty remove-snap script still works.
Debian stable only uses LTS kernel releases, so unfortunately you’ll need to wait for it to appear in
trixie-backports.I hadn’t considered Trixie. Regular Backports is at 6.13, is Trixie ar 6.14?
Ah, I assumed you were just talking about the upcoming release. AFAIK
trixie-backportsdoesn’t exist yet though.
Yeah, I just finally updated the last remaining servers to bookworm this weekend, so a next release is probably coming soon. Proven by earlier experiences
Dude chill it’s not crypto
You’re just mad your distro hasn’t MOONED
The day I do the old fashioned
sudo apt update && sudo apt upgradeand everything suddenly breaks is when I know I’m on Debian 13.deleted by creator
unless they have
stableinstead ofbookwormon theirsources.listdeleted by creator
If you didn’t mess with your sources.list it won’t switch to the new release automatically.
debian updates usually go pretty smooth in my personal experience. last time i had an annoying problem with the nvidia proprietary drivers, but that was an exception (i had no such problem in previous updates) and i think it was my fault
Why would that break on Debian 13?
i made a spreadsheet of debian release dates, graphed the days between releases and calculated a probable release date based on last release date + average days between releases* +/- 1 std deviation
if i remember correctly, bookworm was within my predicted range (apr-aug 2023, i think) and we’re now fully within trixie’s predicted range
*before etch (4.0), release intervals varied wildly, so I don’t take those into consideration
Yeah, nowadays it’s just every other year around June. Linux has become so boring ;)
debian is boring as hell and that’s why i love it
That’s a nice graphic. I’d love to see something comparing it to a rolling release or fedora.
Unfortunately, it wouldn’t tell you anything because you’d compare apples with oranges.
But since opensuse has a (multiple) stable and rolling release, how would it look there? More like the testing release?
For OpenSUSE, they’d probably have two different graphs.




