Or should I go 11 > 12 > 13?
Edit: Thanks for all the replies. I asked this out of laziness and apparently trying this is not a lazy thing to do. I’m not Bilbo Baggins seeking an adventure. Will go with 11 > 12 > 13 way, though might stay at 12 for a while at this point. You know, lazy. :)
Edit 2: Updated to 12. Haven’t checked all the configs yet but so far so good, at least every function I expect works. If I finish this checking sequence, I might go for 13 soon too.
Edit 3: Updated to 13 as well. It actually took shorter than updating from 11 to 12. Though for some reason Jellyfin is marked as obsolete, however it works and I couldn’t care less. My things are working and hopefully I won’t see problems. If I do, I’ll check them one by one at this point since it’s a small home server.
Gotta add this: I had 325 packages on Debian 11, and now I have 450 packages on Debian 13. Some of them are marked as obsolete but must review them one by one. I feel like this upgrade process brake my minimalism and introduced some bloat but gotta care about that later.
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.
Yeah, no idea why it was marked as obsolete but at least I didn’t have to meddle with configs for that. Maybe because of upgrading 2 versions in a row.