Package: bip Version: 0.8.9-1.2 Severity: normal Dear Maintainer,
I have noticed that my bip server did stop to start properly. This seems to be linked to the 'ENABLED' environment variable. Since I renamed it to 'BIP_ENABLED' it worked again. It may be a collision between two environment variables with the same name. As, 'ENABLED' is quite common, I would advise to change this variable to 'BIP_ENABLE' in order to have a clear namespace for this variable and prevent collision with other environment variables. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bip depends on: ii adduser 3.117 ii libc6 2.26-6 ii libssl1.1 1.1.0g-2 ii lsb-base 9.20170808 bip recommends no packages. bip suggests no packages. -- Configuration Files: /etc/init.d/bip changed: --- /etc/init.d/bip~ 2018-02-20 09:47:30.298149760 +0100 +++ /etc/init.d/bip 2018-02-20 10:04:12.320846488 +0100 @@ -23,7 +23,7 @@ DAEMON_ARGS="-f $DAEMON_CONFIG -s $DAEMON_HOME" DAEMON_USER=bip DAEMON_GROUP=bip -ENABLED=1 +BIP_ENABLED=1 # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 @@ -34,7 +34,7 @@ # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME -test "$ENABLED" != "0" || exit 0 +test "$BIP_ENABLED" != "0" || exit 0 # Load the VERBOSE setting and other rcS variables . /lib/init/vars.sh -- no debconf information
