Package: ifupdown Version: 0.7.43 Severity: normal Dear Maintainer,
Since ifupdown 0.7.43 entered testing, I have noticed "ifup -v lo" and "ifdown -v lo" attempting to bring the loopback interface up/down twice. I guess this is because ifup/ifdown now predefine lo internally as an auto interface. They bring lo up/down once for the internal definition and once for the definition in /etc/network/interfaces (which will be present in almost all systems upgraded from wheezy). Unless ifup/ifdown can be made smarter about dealing with multiple definitions, perhaps you should recommend that all mention of lo be omitted from /etc/network/interfaces from now on? The documentation available via "man interfaces" and in /usr/share/doc/ifupdown/examples would need changing to reflect this. Regards, Matthew -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.10 ii initscripts 2.88dsf-41 ii iproute 20120521-3+b4 ii libc6 2.17-3 ii lsb-base 4.1+Debian9 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5+deb70u3 ii net-tools 1.60-25 ii ppp 2.4.5-5.1+b1 pn rdnssd <none> -- 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
