Trixie is 14 months old now
I upgraded to Trixie. Stuff broke.
I rolled back to Bookworm, which was extremely painful, because unlike other OSes rollback is not possible and a reinstall is necessary.
Stuff worked again.
Maybe I'll give it another go in 2028 when it goes EOL. Or maybe not. I'm not under any obligation to keep trying.
Your comment is devoid of any useful technical detail on what broke or why, and quite frankly reads like a very linux noob complaint. Leading me to think you did something wrong in the upgrade process, or failed to manually handle any basic configuration files that you were prompted with diffs/merge/install/keep existing version in the upgrade process.
Why is your first reaction is to assume the person broke something in the upgrade process or did something in the config files? The parent comment is devoid of useful technical detail, but assuming the user is at fault is terrible. Debian is very conservative between releases with not upgrading packages from upstream and keeps a lot out of tree patches. It is very possible something broke between the major versions.
FWIW people use the very same words when they forgot to turn on the monitor or plug their desktop computer to an outlet.
The user who is just complaining without providing any sort of useful information that could be used to help them?
Not sure how it’s any less valid than your anecdotal experience.
Leaving hundreds of unpatched security vulnerabilities open hardly seems "solving"
If you don't report the bugs of what breaks (possibly while it's in testing) nobody can help you.
As an alternative you can report a general bug that will end up on the debian-devel mailing list where someone might reassign it to the proper place. But low effort reports sent to generals are basically a waste of everyone's time.
I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade...
The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old pkg.conf.
Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades.
Although you can set this up after the fact (converting ext4 to btrfs is supported and you can update your mounts from any recovery distro), that's probably just something to keep in mind for your next fresh install. It's also extremely for any other kind of failed upgrade, though, not just full OS upgrades.
(I guess tar czf would work)
That doesn't help if you need to run a piece of software only certified to run under a certain Java version or, worse, a certain OS version. It's either "run on something really old" or "lose the ability for commercial support / you're on your own if shit happens".
Yeah I get it, vendors want to keep their support matrix small. But RHEL (and its bunch of derivatives) just plain suck ass. At least offer support for something based on Debian...
Containers seem lightweight and magical until the tyranny of the quirks of the kernel matters with some gotchas of supported configurations as opposed to unsupported gremlins running custom stuff that other vendors refuse to touch.
> "lose the ability for commercial support / you're on your own if shit happens"
is not something you can clever your way into. It's the vendors choice what support characteristics look like.
Both bookworm and trixie contain the obsolete OpenJDK v8 JRE for both amd64 and ppc64el as it's needed for nvidia-visual-profiler.
These people will need to upgrade at some point, though that point will probably be at the very last moment midway through 2028 if they're still on oldstable today.
Alternatively, if only there were a way to run a contained instance of dovecot 2.3, something like https://hub.docker.com/layers/dovecot/dovecot/2.3.21.1/image...
"Last pushed: over 2 years", while Dovecot 2.3 in Debian Bookworm still receives security patches backported from 2.4 through Debian LTS [1]. Backporting (and LTS in general) certainly isn't bulletproof, but I would prefer it over an abandoned Docker image.
[1] https://tracker.debian.org/news/1817828/accepted-dovecot-123...
And it has been the case for literally decades.
"It's inside our VPN, no customer accesses that server, what could happen?"
We upgraded only to be able to run a newer Java version.
Often there are unresolved compatibility issues across Debian versions. Some are not necessarily tied to the kernel but other components.
"Just upgrade bro" can be a recipe for punishment.