[Piuparts-devel] MBF for obsolete conffiles - help needed

[Herbert Fortes]

Hi,


On 3/28/19 2:20 PM, Andreas Beckmann wrote:
> Hi,
> 
> we already have the data:
> https://piuparts.debian.org/stretch2buster/obsolete_conffiles_issue.html
> but so far we haven't been acting on it.
> 
> But I just analyzed a piuparts failure in buster caused by an obsolete
> logrotate config file from jessie that didn't get cleaned up on the
> upgrades to neither stretch nor buster: #925353
> 
> I'm not going to do the MBF myself (300 packages as of now), but I'll
> gladly help reviewing a template.
> 
> I'd say Severity: important for now, but we should discuss early in the
> bullseye release cycle whether to make them RC for bullseye.
>

The 'adequate' command ask to use 'UserTags' too. I did not add it
because maybe 'piuparts' group all commands used.

Here is a template for review:

To: submit at bugs.debian.org
Subject: obsolete conffiles (policy 10.7.3):

Package:
Version:
Severity: important
User: debian-qa at lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package has obsolete
conffiles. There may be false positives, e.g. if a conffile was
converted to a maintainer script managed configuration file.

To see the policy statement,
https://www.debian.org/doc/debian-policy/ch-files.html#behavior

10.7.3: "[...] Obsolete configuration files without local changes
should be removed by the package during upgrade.[11]"

[11] The dpkg-maintscript-helper tool, available from the dpkg
package, can help for this task. (man dpkg-maintscript-helper)

To see the log file, use the link below and look for the package:
https://piuparts.debian.org/stretch2buster/obsolete_conffiles_issue.html

To find the lines in the log file look for "OBSOLETE CONFFILE".

See also https://wiki.debian.org/DpkgConffileHandling




cheers,



Regards,
Herbert