On 05/08/2013 12:40 PM, Bob Proulx wrote:
Frank McCormick wrote:
Booted up my Sid partition this morning and found the network failed
to initialize. A message during boot said something to the effect
auto lo had been declared twice in /etc/network/interfaces and then
that the same file was unreadable.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707052
There were two different bugs. Here is the entire set:
//snip//
Yes. Now that Wheezy has released Sid is once again very Unstable.
The last year that Sid has been frozen has made Sid relatively
"stable". But now the floodgates are open again and everyone is
pushing changes, sometimes untested changes, into Sid again. For the
next few months it will be exceptionally rough there as a year's worth
of pending disruptive changes are pushed through. If you are using
Sid then you must be able to track problems in the BTS and be able to
use snapshot.debian.org to recover previous versions of packages and
return to them as bugs appear. You might consider using Testing
Jessie instead as it will be somewhat insulated from the thrash in
Unstable Sid.
Let the calamity begin!
Bob
Sounds like a good idea. I like running bleeding-edge software but
not if I have to spend a lot of time on the BTS :)
Can I just make a simple change in my sources list to "testing" and wait
for everything to catch up? I have run Sid for years and it **seems**
that it wasn't this disruptive ? (see my other message about apt-get
wanting to purge gedit and rhythmbox etc)
--
Cheers
Frank
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/518a84f1.9040...@videotron.ca
