Package: apache2-suexec-custom
Version: 2.4.16-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...
This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."
https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.
In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.
>From the attached log (scroll to the bottom...):
Setting up apache2 (2.4.16-1) ...
Configuration file '/etc/apache2/conf-available/security.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** security.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package apache2 (--configure):
end of file on stdin at conffile prompt
This was observed while doing a wheezy -> jessie -> stretch upgrade test.
I did not see such behavior while testing the other apache packages.
cheers,
Andreas
Attachment:
apache2-suexec-custom_2.4.16-1.log.gz
Description: application/gzip