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.

  • non_burglar@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    3 days ago

    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.devOP
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      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.

      • Jess@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        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.devOP
          link
          fedilink
          arrow-up
          1
          ·
          23 hours 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.