5 ms·
Debian's signature feature (upgrade from stable to stable under 15 minutes) shines here too. My first system migrated in less than 10 minutes, incl. package do
by bayindirh 1y ago
Debian's signature feature (upgrade from stable to stable under 15 minutes) shines here too.
My first system migrated in less than 10 minutes, incl. package downloads and reboot. It's not a beast either. N100 mini PC connected to a ~50mbps network.
- mr_sturd 1y agoWhat was the process for this? Does it involve manually modifying the sources.lists files, or is there a single command to instigate the upgrade?
- bayindirh 1y agoThere are two main ways: If your sources file references the release name (e.g.:bookworm), you change them to trixie, then “apt update && apt dist-upgrade”. or, If your sources file directly reference distro-suites (e.g.: stable), you just “apt update && apt dist-upgrade” since stable is now pointing to trixie. In the first reboot, you run “apt autopurge” to remove packages which are not needed anymore. …and you’re done.
- account42 1y agoIs this really a signature feature when rolling release distros are common?
- bayindirh 1y agoYes, esp. if you are using Debian at infra and in production. I upgraded three servers in the morning while sipping my tea. Nobody noticed anything. For RedHat family, this is nigh impossible, requiring hours of planning, downtimes, etc., and even then, it's not guaranteed to work. If you prefer a rolling release, and won't use it on a server, Debian Testing got you covered (unless you are in a security sensitive environment). My systems are well-isolated from outside, so desktop systems can run Testing without issues. Servers and exposed systems always run stable with security updates installed automatically, though.