Bug#672851: netbase 5.0: network connection does not come up upon reboot
On Sat, 2012-05-19 at 22:40 +0100, Adam D. Barratt wrote: On Sat, 2012-05-19 at 19:55 +0100, James Bottomley wrote: On Sat, 2012-05-19 at 16:19 +0200, Marco d'Itri wrote: There is no bug, just don't do stupid things to your system. Yes, there is. The bug is that testing breaks networking on an upgrade and will do so for at least the next six days. No, it won't. ifupdown |0.7~rc3 | testing | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc Great ... that's all I asked for: acceleration of ifupdown or backoff of netbase in testing. This bug can be closed now. James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672851: netbase 5.0: network connection does not come up upon reboot
Package: netbase Version: 5.0 Followup-For: Bug #672851 This bug is still present in testing It means that anyone who does a dist-upgrade -t testing gets no networking. This just happened to me with a co-lo box resulting in a wasted hour investigating the source of an apparent boot failure. This is a really serious problem. It may be fixed by ifupdown-0.7~rc3 but that's stuck in unstable for another 6 days according to http://bjorn.haxx.se/debian/testing.pl?package=ifupdown Having networking break on dist upgrade to testing for another six days (at least) looks to be irresponsible to say the least. Please revert the netbase update or accelerate ifupdown into testing. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages netbase depends on: ii lsb-base 4.1+Debian3 Versions of packages netbase recommends: ii ifupdown 0.7~alpha5+really0.6.16 netbase suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672851: netbase 5.0: network connection does not come up upon reboot
On May 19, James Bottomley james.bottom...@hansenpartnership.com wrote: It means that anyone who does a dist-upgrade -t testing gets no networking. This just happened to me with a co-lo box resulting in a Don't do it then ffs. There is no bug, just don't do stupid things to your system. -- ciao, Marco signature.asc Description: Digital signature
Bug#672851: netbase 5.0: network connection does not come up upon reboot
On Sat, 2012-05-19 at 16:19 +0200, Marco d'Itri wrote: On May 19, James Bottomley james.bottom...@hansenpartnership.com wrote: It means that anyone who does a dist-upgrade -t testing gets no networking. This just happened to me with a co-lo box resulting in a Don't do it then ffs. Interesting idea, but back to the real world where people do actually upgrade their systems, telling them not to isn't so hot for all those new release things people do. There is no bug, just don't do stupid things to your system. Yes, there is. The bug is that testing breaks networking on an upgrade and will do so for at least the next six days. James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672851: netbase 5.0: network connection does not come up upon reboot
On Sat, 2012-05-19 at 19:55 +0100, James Bottomley wrote: On Sat, 2012-05-19 at 16:19 +0200, Marco d'Itri wrote: There is no bug, just don't do stupid things to your system. Yes, there is. The bug is that testing breaks networking on an upgrade and will do so for at least the next six days. No, it won't. ifupdown |0.7~rc3 | testing | source, amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc There's been at least one dinstall and mirror push since that happened. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672851: netbase 5.0: network connection does not come up upon reboot
Hi there! On Mon, 14 May 2012 11:18:28 +0200, Marco d'Itri wrote: On May 14, Adam Warner li...@consulting.net.nz wrote: Multiple Debian sid operating systems (amd64 and i386): Could not connect to them over the network after dist-upgrade and reboot. Isolated cause to netbase 5.0 (which also removes ifupdown). Only if you actually *agree* to remove ifupdown, which most people will probably recognize to not be the wisest move... Andrew, I mistakenly tought that = 0.7~rc1 already was in unstable: either you upload it today or I will have to revert this change (and I do not want to). FYI, no problem here, `apt-get upgrade` pulled: --8---cut here---start-8--- 2012-05-15 16:13:58 upgrade ifupdown:amd64 0.7~alpha5+really0.6.16 0.7~rc3 2012-05-15 16:13:59 upgrade netbase:all 4.47 5.0 --8---cut here---end---8--- So I guess this bug should be closed with ifupdown_0.7~rc3. Thx, bye, Gismo / Luca pgpIa03N18Mj2.pgp Description: PGP signature
Bug#672851: netbase 5.0: network connection does not come up upon reboot
Package: netbase Version: 5.0 Severity: critical Multiple Debian sid operating systems (amd64 and i386): Could not connect to them over the network after dist-upgrade and reboot. Isolated cause to netbase 5.0 (which also removes ifupdown). Workaround if physical access is available to affected servers: 1. obtain ifupdown 0.7~alpha5+really0.6.16 and netbase 4.47 packages for your architecture. Copy *.deb packages to USB key. 2. Mount USB key in affected servers and copy the *.deb packages to /var/cache/apt/archives/ 3. apt-get install ifupdown netbase/testing 4. Verify /etc/init.d/networking restart brings up the network interface before rebooting. 5. Extra precaution: echo netbase hold | dpkg --set-selections to ensure netbase is not upgraded again until this is sorted out. This message is a quick warning for others. I understand I have not provided enough information about my systems for debugging purposes. I just want to limit the number of people potentially affected by this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672851: netbase 5.0: network connection does not come up upon reboot
On May 14, Adam Warner li...@consulting.net.nz wrote: Multiple Debian sid operating systems (amd64 and i386): Could not connect to them over the network after dist-upgrade and reboot. Isolated cause to netbase 5.0 (which also removes ifupdown). Only if you actually *agree* to remove ifupdown, which most people will probably recognize to not be the wisest move... Andrew, I mistakenly tought that = 0.7~rc1 already was in unstable: either you upload it today or I will have to revert this change (and I do not want to). Workaround if physical access is available to affected servers: Actually the fix is much simpler: just run ifup -a from the console and then install ifupdown from experimental, or copy /etc/init.d/networking from any Debian system. -- ciao, Marco signature.asc Description: Digital signature
