Hello everyone! It’s been about a month that I’m experimenting Debian on an external disk. For the most time, I’ve been using Testing. The issue is, that some packages are missing from Testing, while they exist on Stable (or on Unstable). The biggest problem with that is that some packages require dependencies that don’t exist on the Testing repo and as such I can’t install those apps.
So, I thought about adding the Stable repo, at a lower priority. If something doesn’t exist on Testing, it will grab it from Stable.
How bad is that approach? I’m not doing the reverse (using stable and grabbing apps from testing), which might be way worse. Does anyone else do that? I couldn’t find anything related online.
PS. I’m a bit tempted to switch to Unstable all together, but I don’t know if I’ll be careful enough to use it in the long run.
PPS. I might build a home nas at some point (with Debian Stable) and keep regular backups of my laptop so that I’ll be kinda safe if I ever switch to Unstable.
I see I see, thank you for you quick reply. This tempts me even more to use sid, hmm.
This is a different question from the original post, but do you happen to know what to do when listbugs warns me that a package has bugs? I suppose almost all packages have some bugs to some degree. Should I just avoid them on Sid? Or should I check how bad the bug is (if it belongs to a serious category) and decide whether to update it?
I say the solution is one step earlier. Backups and snapshots.
Use BTRFS or ZFS filesystem on your install and use snapshots to be able to rollback if things go bad.
Here’s an example on how to set up BTRFS with automatic snapshots:
https://github.com/david-cortes/snapper-in-debian-guide
For backups Borg is popular:
https://github.com/borgbackup/borg