Package: ifupdown Version: 0.8.18 Severity: normal Dear Maintainer,
It looks like ifquery --state return the opposite exit code of what it's supposed to. If the queried interface is up, it will exit with the status code 1. If one of the queried interface is down or doesn't exist, it exits with status code 0. It also exits with an error when the queried interface isn't specified. This bug has been introduced with the version 0.8.18 (exactly by the commit c3cf84e) and might break some scripts that rely on the exit code. Best regards, Celelibi -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages ifupdown depends on: ii adduser 3.115 ii init-system-helpers 1.46 ii iproute2 4.9.0-1 ii libc6 2.24-8 ii lsb-base 9.20161125 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5-3 Versions of packages ifupdown suggests: pn ppp <none> pn rdnssd <none> -- debconf information excluded
