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: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707041 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707048 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707048 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707052 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707054 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707092 > These are the changes apt-get made yesterday before this problem > surfaced..but to me it doesn't seem any of the packages would > change networking Somewhere along the way you upgraded 'ifupdown' from 0.7.8 that it had been to 0.7.41 or 0.7.42. > Can anyone provide any insight ? 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
signature.asc
Description: Digital signature
