AdrianTM wrote:There's no hacker in my grandma...
dilberts_left_nut wrote:No point auto-checking - there will always be updates, and you will need to evaluate them manually anyway if you don't want it to blow up.
aptitude is what i would recommend for sid.
zoli62 wrote:More specifically, I installed the system from testing iso. Then in source.list I replaced Bullseye with unstable. What are the risks of going back to the testing branch?
sunrat wrote:zoli62 wrote:More specifically, I installed the system from testing iso. Then in source.list I replaced Bullseye with unstable. What are the risks of going back to the testing branch?
Testing is generally regarded to be less reliable than Sid. It can take many days for upstream bug fixes and security updates to filter from Sid to Testing.
For production, use Stable.
AdrianTM wrote:There's no hacker in my grandma...
The use of testing or unstable is a lot of fun but comes with some risks. Even though the unstable suite of the Debian system looks very stable for most of the times, there have been some package problems on the testing and unstable suite of the Debian system and a few of them were not so trivial to resolve It may be quite painful for you. Sometimes, you may have a broken package or missing functionality for a few weeks.
Debian users pride themselves on being able to deal with pain [...]
apt-get update && apt-get install $(debsecan --suite sid --format packages --only-fixed)
aptitude update && aptitude install $(debsecan --suite sid --format packages --only-fixed)
anticapitalista wrote:IMO anyone using sid (I do) just needs to read the output of apt-get dist-upgrade and not blindly press Enter. No need for apt-list-bugs.
Sure it helps if you use a windows manager rather than a complex desktop-environment like ....
Users browsing this forum: No registered users and 3 guests