Your message dated Thu, 25 Jun 2015 15:59:06 +0200
with message-id <20150625135906.ga28...@mail.beuc.net>
and subject line Re: fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): 
/etc/exim4/exim4.conf.template 
/etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs
has caused the Debian Bug report #789772,
regarding fusionforge-mta-exim4: modifies conffiles (policy 10.7.3): 
/etc/exim4/exim4.conf.template 
/etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs
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.)


-- 
789772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fusionforge-mta-exim4
Version: 6.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
And these are not even conffiles shipped by your package.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-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...):

0m52.1s ERROR: FAIL: debsums reports modifications inside the chroot:
  /etc/exim4/exim4.conf.template
  /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs


cheers,

Andreas

Attachment: fusionforge-mta-exim4_6.0.1-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Hi,

> during a test with piuparts I noticed your package modifies conffiles.

That's indeed the point of "fusionforge-mta-exim4", which is meant to
configure exim4 for fusionforge integration.

> And these are not even conffiles shipped by your package.
> This is forbidden by the policy, see
> https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

Your excerpts mentions generalities about [generated] conffiles; they
do not explain why this would be forbidden by policy.

> 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!).

That's what we do: changing the conffile while preserving user
customizations.  And removing that change on uninstall.


It looks like you're reporting a bug through automated means, without
actually using the package, so please only send bugs that are relevant
(as checking this is quite time-consuming, plus we didn't volunteer to
beta-test piuparts) and preferrably with a patch.
Alternatively leave the FusionForge packages alone.

Closing.
Sylvain

--- End Message ---

Reply via email to