Package: adequate
Version: 0.15.3
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Adequate reports obsolete-conffile if a package no longer ships a
conffile, but there are two cases to distinguish:
• the package’s buggy and didn’t clean up
• dpkg didn’t remove the conffile because it was locally changed
Only the first one should result in a bugreport to the maintainer
of the package. Can you please distinguish these somehow?
Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages adequate depends on:
ii debconf 1.5.74
ii perl 5.32.1-2
Versions of packages adequate recommends:
pn pkg-config <none>
adequate suggests no packages.
-- Configuration Files:
/etc/apt/apt.conf.d/20adequate changed:
// If you set this to "true", adequate will run on every install, reporting the
// results via debconf.
Adequate::Enabled "true";
DPkg::Pre-Install-Pkgs {
"adequate --help >/dev/null 2>&1 || exit 0; exec adequate --user nobody
--tags -bin-or-sbin-binary-requires-usr-lib-library --apt-preinst";
};
DPkg::Post-Invoke {
"adequate --help >/dev/null 2>&1 || exit 0; exec adequate --user nobody
--tags -bin-or-sbin-binary-requires-usr-lib-library --pending";
};
DPkg::Tools::Options::adequate::Version "2";
-- no debconf information
