3 ms·
Do you have to do explicit upgrades for e.g. 11 -> 12, or how does it work with sid? It sounds like maybe not.. > From a software developer's point of view, D
by metadat 2y ago
Do you have to do explicit upgrades for e.g. 11 -> 12, or how does it work with sid?
It sounds like maybe not..
> From a software developer's point of view, Debian Sid and Arch are both "unstable" release streams. That means that they don't have versioned releases; they just have one indefinite release stream. There is no formal schedule or window for any class of changes.
- JonChesterfield 2y agoSid is a rolling release in the same fashion as other distros. New code comes in whenever you update which probably works sanely but might be transiently broken. If you follow "testing", you get a slightly strange cadence where things change quickly just after a stable release and gradually slows down until stable is created, then picks up pace again. A reasonable choice is to follow whichever named release is currently in testing. Currently that's "trixie". It's identical to the testing release until the fork happens, at which point the local install will be an instance of stable. It's very easy to forget you've done that until you notice some program you're running is older than you expected, at which point upgrading to testing to find the newer one is straightforward. The machine I'm writing this on is running debian unstable. Installed ~ four years ago when I bought the machine, expecting it to continue working until the nvme burns out.
- jcelerier 2y agoHaving used Debian stable, then testing, then sid, then migrated to archlinux, I can very confidently say that an arch Linux system will break infinitely less than Debian testing & sid
- SauciestGNU 2y agoMy use case is mainly containerization and container orchestration, but in 12 years I've had Sid break on me once, and testing never. Maybe I got lucky.