Linux

58319 readers

1105 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[Solved] Can I upgrade my server directly from Debian 11 to 13 without problems? (programming.dev)

submitted 5 days ago* (last edited 3 days ago) by muhyb@programming.dev to c/linux@lemmy.ml

26 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] non_burglar@lemmy.world 19 points 5 days ago (1 children)

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.

[–] muhyb@programming.dev 8 points 5 days ago (1 children)

I know what I'm doing but looking at every comment here, it's not a wise thing to do it seems. So casual or not 11 > 12 > 13 is the proper and most likely still the easiest way. It's a good thing that I asked before doing some potentially mad thing.

[–] non_burglar@lemmy.world 4 points 5 days ago (1 children)

Honestly, there were so many fundamental changes in the 13 upgrade for certain packages that I had to fix on a couple of machines that I'd be hesitant to try no-scoping the 11 > 13 upgrade.

I flew by the seat of my pants and managed to pull off 10 directly to 12, but I wouldn't do it for this one.

[–] muhyb@programming.dev 1 points 5 days ago (1 children)

Well, if there are issues like even in normal upgrade, it's better not to jump on a thing like this.

Still, it's good to know that this is technically possible, though it's not for a lazy person who just wants to update his server. Gotta check Debian changelog.

[–] LaSirena@lemmy.world 2 points 4 days ago (1 children)

I did it by accident last week on a long running VM. It was rough because I also had the official docker repo as a source. I was stuck in a partial state for a while and only a lot of googling helped. Only recommended if you're bored.

[–] muhyb@programming.dev 1 points 3 days ago

Oh, partial upgrade is the worst. Technically it's still supported until next year as oldoldstable so it should be fine to directly upgrade if you ask me but I understand the changes affect many things and upgrade process actually check things from the previous version, so if one upgrade directly it might go bad. That's probably why Arch Linux can get borked if you haven't updated for a long time.