On 28 February 2014 10:36, Andreas Beckmann <a...@debian.org> wrote:
> Package: maradns
> Version: 2.0.09-1
> Severity: serious
> User: debian...@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
> http://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."
>
> http://wiki.debian.org/DpkgConffileHandling should help with figuring
> out how to do this properly.
>
> In http://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 maradns (2.0.09-1) ...
>   Installing new version of config file /etc/init.d/maradns ...
>
>   Configuration file '/etc/maradns/mararc'
>    ==> File on system created by you or by a script.
>    ==> File also in package provided by package maintainer.
>      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.
>   *** mararc (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
> maradns (--configure):
>    EOF on stdin at conffile prompt
>   Errors were encountered while processing:
>    maradns
>
>
> To fix this, one has probably to undo modifications performed
> on the conffile by the maintainer scripts in wheezy.
>


I am on it. It is a bug that emerged as a side effect of closing [1],
where previous maintainer modified config files.
So apparently I have not fixed it completely.

So if I understand this correctly if I fix this, I will be back with
[1],  because now I do not modify conffiles, just copy them from
upstream as they are. If I revert to modifying the conffile, I will
still be violating 10.7.3 again. Undoing modifications performed in
wheezy is what I do now. I need somebody to talk me through this, Ill
talk to befriended DD.



[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710903


-- 
Pozdrawiam,
Dariusz Dwornikowski, Assistant
Institute of Computing Science, PoznaƄ University of Technology
www.cs.put.poznan.pl/ddwornikowski/
room 2.7.2 BTiCW | tel. +48 61 665 29 41


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to