Your message dated Mon, 17 Apr 2017 18:03:09 +0200 with message-id <[🔎] 20170417160309.GK23022@beskar.mdcc.cx> and subject line Re: Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css has caused the Debian Bug report #699744, regarding wheezy-manual: strongly suggest to upgrade dpkg first 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 owner@bugs.debian.org immediately.) -- 699744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699744 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css
- From: Andreas Beckmann <anbe@debian.org>
- Date: Mon, 04 Feb 2013 13:28:10 +0100
- Message-id: <20130204122810.5846.52707.reportbug@cake.ae.cs.uni-frankfurt.de>
Package: nagios3-cgi Version: 3.4.1-2 Severity: serious User: debian-qa@lists.debian.org Usertags: piuparts Control: affects -1 + nagios 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 was observed on an upgrade from lenny to squeeze to wheezy. 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 nagios3-cgi (3.4.1-2) ... Configuration file `/etc/nagios3/stylesheets/outages.css' ==> 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. *** outages.css (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing nagios3-cgi (--configure): EOF on stdin at conffile prompt cheers, AndreasAttachment: nagios3_3.4.1-2.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
- To: Antoine Beaupre <anarcat@debian.org>, 699744-close@bugs.debian.org
- Cc: 699744@bugs.debian.org, Andreas Beckmann <anbe@debian.org>, Vagrant Cascadian <vagrant@debian.org>
- Subject: Re: Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css
- From: Joost van Baal-Ilić <joostvb-debian-bugs-20130406-3@mdcc.cx>
- Date: Mon, 17 Apr 2017 18:03:09 +0200
- Message-id: <[🔎] 20170417160309.GK23022@beskar.mdcc.cx>
- In-reply-to: <[🔎] 20170417132230.ejhlpmnuv4ea6qef@curie.anarc.at>
- References: <20130406072925.GA19314@beskar.mdcc.cx> <[🔎] 20170417132230.ejhlpmnuv4ea6qef@curie.anarc.at>
On Mon, Apr 17, 2017 at 09:22:30AM -0400, Antoine Beaupre wrote: > On Sat, Apr 06, 2013 at 09:29:25AM +0200, Joost van Baal-Ilić wrote: > > Hi, > > > > I agree with Andreas Beckmann it would be useful if a remark could be > > added to the release notes. I can apply a patch soon. Below snippets > > from previous discussion summarize the relevant parts I believe. > > Anybody willing to draft a patch? > > This bug has been inactive for more than 4 years, and wheezy is now LTS. > Is this still relevant, or should we just close this bug already? Could better be closed, imho. Just doing that now. Thanks for triaging! Bye, Joost
--- End Message ---