Bug#1035483: debsums: false positives on removed conffiles retaining a remove-on-upgrade entry in Conffiles

[Andreas Beckmann]

Package: debsums
Version: 3.0.2
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts

After a piuparts upgrade of pkg-config from bullseye to bookworm,
the package status is

# dpkg -s pkg-config
Package: pkg-config
Status: install ok installed
Priority: optional
Section: oldlibs
Installed-Size: 29
Maintainer: Andrej Shadura <andrewsh at debian.org>
Architecture: amd64
Multi-Arch: same
Source: pkgconf
Version: 1.8.1-1
Depends: pkgconf (>= 1.8.0-7~)
Conffiles:
 /etc/dpkg/dpkg.cfg.d/pkg-config-hook-config 467c877de00898418a9b26d432a1719a remove-on-upgrade
Description: manage compile and link flags for libraries (transitional package)
 pkgconf is an implementation of the pkg-config system, which helps to configure
 compiler and linker flags for development frameworks.
 .
 pkgconf is a replacement for pkg-config, providing additional functionality
 while also maintaining compatibility.
 .
 This package only provides a dependency link to the pkgconf package to help
 with package upgrades. It can be safely removed.
Homepage: http://pkgconf.org/

and debsums complains:

# debsums -ac --ignore-obsolete pkg-config ; echo $?
debsums: missing file /etc/dpkg/dpkg.cfg.d/pkg-config-hook-config (from pkg-config:amd64 package)
2

while after a fresh install in bookworm the Conffiles entry is
different:

Conffiles:
 /etc/dpkg/dpkg.cfg.d/pkg-config-hook-config newconffile remove-on-upgrade

and debsums does not complain:

# debsums -ac --ignore-obsolete pkg-config ; echo $?
0

I assume that dpkg is correct and debsums is at fault here ...

A quick fix that works for me (and piuparts) is in line 268

-                grep { not ($ignore_obsolete and / obsolete$/) }
+                grep { not ($ignore_obsolete and / (obsolete|remove-on-upgrade)$/) }


Andreas