Package: mount Version: 2.28-1 Severity: important Amusing, right? But not too much.
It does actually happen due to a new behavior in libselinux, which mount links against. The same is true for any binary in util-linux and coreutils (and so on) See bug #822679 I consider this behavior unexpected. [and yes, I'm doing this to raise some awareness. Close the report if needed] -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mount depends on: ii libblkid1 2.28-1 ii libc6 2.22-7 ii libmount1 2.28-1 ii libselinux1 2.4-3+b1 ii libsmartcols1 2.28-1 ii libudev1 229-5 mount recommends no packages. Versions of packages mount suggests: pn nfs-common <none>
