Hello! I’m thinking about switching from my beloved fedora to a rolling release distro, because it really intrigues me, but I’m a bit scared of Arch, it’s still too soon for me to go down this rabbit hole XD
what do you think about debian testing? It’s not a “true” rolling release as long as I understand, but it “practically” behaves like one, correct? On the system informations I still see Debian 12, what will happen when Debian 13 stable will be released?

sorry if these are silly questions and thanks to all in advance!

  • TunaCowboy@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Ignore the uninformed masses.

    Although this is useful information, gratuitous displays of hubris are gross. You should do yourself a favor and keep reading - it is clear that the decision should be up to the user after careful consideration.

    All of the issues in regard to testing have well known mitigations which are trivial to implement. You can find this information and the corresponding links here

    It is a good idea to include unstable and experimental in your apt sources so that you have access to newer packages when needed. With the APT::Default-Release apt config setting or with apt pinning you can have packages from testing by default but if you manually upgrade some packages to unstable or experimental, then you will get upgrades within that suite until those packages migrate down to unstable or testing. The apt pinning needs priorities lower than 990 and equal to or higher than 500 for this to work nicely. You can also pin some packages to unstable/experimental that you always want the latest versions of.

    It is a good idea to install security updates from unstable since they take extra time to reach testing and the security team only releases updates to unstable. If you have unstable in your apt sources but pinned lower than testing, you can automatically add temporary pinning for packages with security issues fixed in unstable using the output of debsecan.

    • Raphael@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      1 year ago

      Thanks for the downvote.

      I didn’t downvote any of your posts, have fun being toxic.

    • Raphael@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      1 year ago

      Although this is useful information, gratuitous displays of hubris are gross.

      Oh, looks like I hit a nerve.

      It is a good idea to include unstable and experimental in your apt sources so that you have access to newer packages when needed. With the APT::Default-Release apt config setting or with apt pinning you can have packages from testing by default but if you manually upgrade some packages to unstable or experimental, then you will get upgrades within that suite until those packages migrate down to unstable or testing. The apt pinning needs priorities lower than 990 and equal to or higher than 500 for this to work nicely. You can also pin some packages to unstable/experimental that you always want the latest versions of.

      It is a good idea to install security updates from unstable since they take extra time to reach testing and the security team only releases updates to unstable. If you have unstable in your apt sources but pinned lower than testing, you can automatically add temporary pinning for packages with security issues fixed in unstable using the output of debsecan.

      And that’s why Windows users say Linux is for nerds. At that point it would easier to switch to Arch, or at least just use Sid and maybe set up some rollback mechanisms.