Package: debian-security-support Version: 2019.12.12~deb10u1 Severity: wishlist Tags: upstream
Dear Maintainer, * What led up to the situation? Two things: 1. I have installed binutils, which is Build-Essential and has limited security support (#948634). 2. I use «chronic -e sh -c 'check-support-status >&2'» to check whether any packages with limited security support are installed. * What was the outcome of this action? Every time I run the command from (2), it exits non-zero, because binutils is installed. * What outcome did you expect instead? I'd like to be to have a way to run, say, «check-support-status --dont-complain-about=binutils,binutils-common,libbinutils,binutils-x86-64-linux-gnu». This command would skip the binary packages given on the command line when looking for and listing installed binary packages with limited support status. Thus, in effect, it would let the admin "whitelist" known issues, so only new ones would be printed. Would this make sense? Cheers, Daniel -- System Information: Debian Release: 10.3 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debian-security-support depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.71 ii gettext-base 0.19.8.1-9 debian-security-support recommends no packages. debian-security-support suggests no packages. -- debconf-show failed
