On 2007-08-06 08:04:16 -0500, Hugo Vanwoerkom wrote: > Brokenness in Unstable: > 1. Research Bugs + google lists. > 2. If you find a hit apply the fix. > 3. If not, wait a while and upgrade again. > > Unstable being Unstable this is the best possible solution.
No, you forgot: tools to handle brokenness, like apt-listbugs and apt-listchanges[*]. Unfortunately they are far from being perfect. Why not improving such tools? [*] A system can get broken due to major changes in packages; such changes are often announced in the NEWS file, and apt-listchanges allows to display new information from the NEWS files. When users don't read NEWS files, they end up with bugs like that: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428882 or more seriously (because I lost mail), like that: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301906 (well, concerning this bug, the config change wasn't announced immediately in the NEWS file). One of the Debian developers said: "NEWS.Debian is a must-read on unstable boxes, and the changelog maybe as well." -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
