Your message dated Mon, 30 Aug 2021 10:14:53 +1000
with message-id
<CAFMei7NRwM+t=kf6+vskobiwjohestukp7duab_s7z2xza-...@mail.gmail.com>
and subject line Re: [pcp] Processed: found 990223 in 5.3.2-1
has caused the Debian Bug report #990223,
regarding pcp-zeroconf: modifies conffiles (policy 10.7.3):
/etc/default/pmlogger
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
990223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcp-zeroconf
Version: 5.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files
10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."
Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).
Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"
If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling
In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.
debsums reports modification of the following files,
from the attached log (scroll to the bottom...):
/etc/default/pmlogger
cheers,
Andreas
pcp-zeroconf_5.3.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Tue, Aug 3, 2021 at 7:29 AM Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
>
> Processing commands for cont...@bugs.debian.org:
>
> > found 990223 5.3.2-1
> Bug #990223 [pcp-zeroconf] pcp-zeroconf: modifies conffiles (policy 10.7.3):
> /etc/default/pmlogger
> Marked as found in versions pcp/5.3.2-1.
>
Upstream have created pcp-zeroconf as a non-default part of the PCP
package suite to automate first-time setup of Performance Co-Pilot for
new users in the same, documented fashion across different distros.
So while it does indeed not meet the packaging requirements here, it is
not a required part of PCP but a convenience mechanism for new users
who are otherwise overwhelmed with the array of choice and in need of
some assistance as to where / how to start.
As such, this is operating as intended, designed and documented. Any
users not wanting this behaviour would not opt-in to using this package.
cheers.
--
Nathan
--- End Message ---
