11-12 should be well tested. 12-13 should be well tested. 11-13 may work, but you may be the tester.
I'd step through one at a time.
11-12 should be well tested. 12-13 should be well tested. 11-13 may work, but you may be the tester.
I'd step through one at a time.
11 > 12 > 13 is way safer!
No.
By itself, apt will give you headaches.
Debian migrated to new paths for security non-free firmware in repositories from 11 to 12, and apt goes to v3 in 12 to 13, which changes the format of sources. There is a new apt modernize-sources command, but it assumes your paths are correct.
If you know what you're doing, you can do this by correcting the repo paths and do the without-new-packages upgrade, but be prepared to fix apt.
If you're a casual user, maybe stick with 11>12>13.
For fixed-release distros (Debian/Ubuntu), the upgrade path is usually sequential.
The main implication: if you skip, you’re outside the tested upgrade path. That can mean broken packages, orphaned configs, security regressions, or a system that simply won’t boot. Sometimes you can force it and it’ll work, but it’s a gamble...
I’m wouldn’t do it. Debian isn’t something that likes big jumps like that. Consider an immutable distro if you want to be able to leap around that way.
Likely not. I've tried skipping a release once by accident (I didn't pay enough attention) and it ended with a bricked system and a full reinstall. Don't do it.
Major version changes for any software from the OS right down to a simple notepad app should update as sequentially as possible (11>12>13>etc). Skipping over versions is just asking for trouble, as it's rarely tested throughly.
It might work, but why risk it.
An example: if 12 makes a big database change but you skip over that version, 13 may not recognize the databases left by 11 because 12 had the code to recognize and reformat the old database while that code was seen as unnecessary and removed from 13.
Stuff like this is also why you can't always revert to an older version while keeping the data/databases from the newer software.
It would be great if more effort was put into ensuring a seamless upgrade experience.
Hey. I'm going through this right now. My server was 11, and I wanted to go to 13. I definitely didn't want to get into a situation where the server required hours and hours of repair.
I'm halfway there. The upgrade to 12 went smoothly. The biggest headache was glances, first from the lack of web interface (which I was ready for), and the lack of RAID support (not ready). I might do the switch to 13 next week.
I feel like 13 introduced more changes than 12. By the way, I finally took the leap and upgraded to 13. Kinda YOLO'd though and it needs some fixing in configs but currently everything I expect works, so this will be a very slow fixing process I reckon. :)
Good luck with the upgrade!
Did you go straight there, or go through 12?
Oh I went 11 > 12 > 13. But haven't really checked all the configs from 12 to 13, there are many new ones too.
Well I finally upgraded to 13, a few months later. The only issue was the blob file in glances, which I was ready to deal with. Oh and I had to install php-mysql.
I don't like that you can't start the Debian upgrade and just walk away. It stops and asks you about configuration files, so you have to babysit it. Other than that, it works well.
That's good news! Mine had some quirks like I had to uninstall and reinstall Jellyfin and some couple things for some reason too.
But yeah, I would like some more automated upgrade as well. Though Debian itself is a manual installation so current situation makes sense.
Interesting. After I got the new Debian running, I just updated the source for Jellyfin (and a few other packages) to Trixie, and it updated just fine.
When I upgraded the desktop and laptop machines, I didn't run into many issues. Had to reinstall the Nvidia drivers on the game machine. And deal with glances, but I mentioned that before.
I'll probably update the server to 13 next week.
I had to rewrite part of my php-based photo management system, as it relied on a library that was originally written for php 4 or 5 and hasn't been updated. Fortunately that wasn't too hard. There might be other things lurking like that, but they aren't critical problems - I can deal with them at leisure.
As someone who went through the 12-13 upgrade last week. Do not go directly. I had to rollback twice during the 12-13 upgrade(thank you timeshift) so I couldn't imagine trying to run an 11-13 upgrade.
all 28 comments