Debian Testing is a great way to try out Debian and provide feedback to the project. But it's not a rolling release Linux distro. Although some successfully use it like one. In today's video, I'll ...
Packages in testing get updated at the times that they can and sometimes this messes with other packages. For example I had pithos installed this morning, in trixie. An upgrade removed a dependency so it had to go. In another day or 3 I will be able to install pithos again, no doubt. Running testing when release is within 9 months since sarge and this is the only issue I have seen. Since it resolves itself, I never saw it as a problem.
Wanted a stable and cool system, so went with debian stable.
But stable was outdated for my taste, so I went to testing.
But testing had missing packets, so I tried to update to unstable, though I did it badly and crashed my system.
After resinstalling testing, I tried to make a semi-failed script to autodownload/update apps outside the debian repo, but I found out that nixos essentially did this, in fact much better. And I accidentally deleted my /usr/bin/ dir with that script, so I eventually went with nixos unstable:)
I mean, the logical step is to go to Debian sid, which, despite its alternative name unstable, is really not. I’ve been running a gaming rig on it for over a year with nothing more than vey vey minor hiccups, mostly because I’m impatient and run apt full-upgrade frequently.
I don't daily drive either distro these days but I've always found Arch to be more stable than Debian testing. I also just really don't like apt. I think its pathetic to not have parallel downloads in 2025.