[Pkg-nagios-devel] Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css

[Vagrant Cascadian]

On Mon, Feb 04, 2013 at 01:28:10PM +0100, Andreas Beckmann wrote:
> This was observed on an upgrade from lenny to squeeze to wheezy.

Installing on squeeze and then upgrading to wheezy seemed to go fine for me.

I did have similar (but not identical) problems with a full lenny -> squeeze ->
wheezy, more on that below...

 
> >>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

I was unable to reproduce this exact issue. Intsalled a chroot with lenny,
upgraded to squeeze, and then upgraded to wheezy... but got a very similar dpkg
conffile prompt for /etc/nagios3/cgi.cfg:

  Setting up nagios3-cgi (3.4.1-2) ...
  Installing new version of config file /etc/nagios3/stylesheets/outages.css ...
  Installing new version of config file /etc/nagios3/stylesheets/checksanity.css ...
  Installing new version of config file /etc/nagios3/stylesheets/history.css ...
  Installing new version of config file /etc/nagios3/stylesheets/tac.css ...
  Installing new version of config file /etc/nagios3/stylesheets/avail.css ...
  Installing new version of config file /etc/nagios3/stylesheets/notifications.css ...
  Installing new version of config file /etc/nagios3/stylesheets/trends.css ...
  Installing new version of config file /etc/nagios3/stylesheets/ministatus.css ...
  Installing new version of config file /etc/nagios3/stylesheets/histogram.css ...
  Installing new version of config file /etc/nagios3/stylesheets/extinfo.css ...
  Installing new version of config file /etc/nagios3/stylesheets/status.css ...
  Installing new version of config file /etc/nagios3/stylesheets/common.css ...
  Installing new version of config file /etc/nagios3/stylesheets/showlog.css ...
  Installing new version of config file /etc/nagios3/stylesheets/statusmap.css ...
  Installing new version of config file /etc/nagios3/stylesheets/config.css ...
  Installing new version of config file /etc/nagios3/stylesheets/summary.css ...
  Installing new version of config file /etc/nagios3/stylesheets/cmd.css ...
  
  Configuration file `/etc/nagios3/cgi.cfg'
   ==> 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.
  *** cgi.cfg (Y/I/N/O/D/Z) [default=N] ? y


As far as I can tell, /etc/nagios3/stylesheets/* were introduced in the squeeze
nagios3-cgi package. /etc/nagios3/cgi.cfg was a conffile with nagios3-common in
wheezy, and transitioned to nagios3-cgi for wheezy. My guess is something wrong
in the transition from nagios3-common to nagios3-cgi for cgi.cfg, but I'm not 
sure what exactly is needed there.


Why my installation had no trouble with /etc/nagios3/stylesheets/outages.css is
a mystery to me. I did not use piuparts, rather just used an schroot with lenny
installed. I did do an "apt-get upgrade" followed by an "apt-get dist-upgrade"
in each of my upgrade cycles, if that somehow matters. Also had etckeeper
installed in order to track the changes in configuration files, which pulled in
a few more package dependencies.


live well,
  vagrant