Your message dated Mon, 18 Jun 2012 09:51:20 +0200
with message-id <4fdeddf8.4000...@enovance.com>
and subject line Re: [Openstack-devel] This is not a bug, it is a feature!
has caused the Debian Bug report #677400,
regarding nova-common: prompting due to modified conffiles which were 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.)
--
677400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nova-common
Version: 2012.1-6
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 nova-common (2012.1-6) ...
Configuration file `/etc/nova/nova.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.
*** nova.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing nova-common
(--configure):
EOF on stdin at conffile prompt
This problem was observed on a distupgrade from wheezy to sid.
cheers,
Andreas
nova-common_2012.1-6.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
On 06/18/2012 08:38 AM, Thomas Goirand wrote:
> On Mon Jun 18 2012 01:06:30 PM CST, Ola Lundqvist <o...@inguza.com> wrote:
>> The statement in the mail to the development list is wrong.
>> Install scripts can modify configuration files if it is done
>> in a safe way preserving local modifications.
> No! If you intend to modify a configuration file
> it shouldn't be marked as such, and should be
> managed by post{inst,rm}.
>
>> Due to this I'm closing this bug now.
> Please reopen it!
>
Could you please provide a patch explaining how you would resolve this release
critical bug ? That will also help understand your position. I'm sure Ola will
then agree to cleanup and integrate the patch that is most agreeable to you.
Thanks in advance for the help :-)
--- End Message ---
