Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
ou can drop my qbittorrent repo you have listed there; it looks like testing is now keeping it current. I also have now added Buster to the compiz-reloaded repository.
Steve,
Great can you help me get my compiz fully working again on my testing computer?
Should I go back to the compiz thead and post some information?
Thanks
Dan
What are some best practices for testing/sid users?
The most important thing is to keep in mind that you are participating in the development of Debian when you are tracking testing or unstable. This means that you should know your way around Linux, Debian and the Debian packaging system and that you should have an interest in tracking down and fixing bugs. There are a couple of things you can do in order to ease your life as a testing/sid user such as:
Always be careful when you perform updates and check if the actions proposed by the package managing tools are in line with your wishes and expectations. (i.e. make sure that you do not remove a plethora of packages you need by blindly accepting the proposed action)
Bearing this in mind, apt-get dist-upgrade to keep your system fully up-to-date, but if the proposed changes do look unreasonable, some of the simpler things that could help are:
put packages on hold until the problem in the archive is resolved,
use apt-get upgrade to avoid removals this time,
simply wait until the archive has settled down to a more reasonable state before upgrading.
Install the apt-listbugs and apt-listchanges packages in order to be made aware of grave bugs or important changes when you install new packages or during an upgrade.
Consider subscribing to debian-devel-announce@lists.debian.org (very low-traffic mailing list, 1 to 10 per month) to be notified on future technical changes or possible problems.
Keep a good live CD/USB such as Debian Live around at all times so you can still work on the system even if it is not booting anymore.
Automatically create daily, weekly and monthly backups in order to ensure that corrupted data is not a problem.
^This thread is for giving advice to new users of Testing, or about sharing your experience with Testing. You should make a new thread for your problem, support questions don't belong here.