Your message dated Tue, 24 Apr 2012 18:00:56 -0500
with message-id <20120424230056.gk26...@gwolf.org>
and subject line Re: collabtive: prompting due to modified conffiles which 
where not modified by the user
has caused the Debian Bug report #664663,
regarding collabtive: prompting due to modified conffiles which where not 
modified by the user
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.)


-- 
664663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: collabtive
Version: 0.7.5-5
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 collabtive (0.7.5-5) ...
  
  Configuration file `/etc/collabtive/config.php'
   ==> 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.
  *** config.php (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing collabtive 
(--configure):
   EOF on stdin at conffile prompt


cheers,

Andreas

Attachment: collabtive_0.7.5-5.log.gz
Description: GNU Zip compressed data


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

While I agree with your bug report, this problem occurs only when
upgrading from ≤ 0.7.5-3 to ≥ 0.7.5-4. That is, affected versions are
not very likely to be present except in a small amount of systems in
testing, and none in stable.

I am closing this bug, not because it is not a real bug, but because
of its very small impact (and the time that would most probably be
invested in fixing it according to the letter). Please reopen if you
disagree with me, and I'll (sigh) take a deep look at it.


--- End Message ---

Reply via email to