Your message dated Wed, 25 Jul 2012 15:54:30 +0200
with message-id <500ffa96.3050...@haasjes.com>
and subject line Re: Bug#680861: aiccu: Breaks dist-upgrade if not correctly 
configured
has caused the Debian Bug report #680861,
regarding aiccu: Breaks dist-upgrade if not correctly configured
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.)


-- 
680861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aiccu
Version: 20070115-15.1
Severity: serious
Justification: Breaks upgrades

Setting up aiccu (20070115-15.1) ...
Files /usr/share/aiccu/conf-templates/aiccu.conf and /etc/aiccu.conf differ
[FAIL] AICCU is not configured, edit /etc/aiccu.conf first ... failed!
invoke-rc.d: initscript aiccu, action "start" failed.
dpkg: error processing aiccu (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 aiccu
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have deliberately commented out some of the fields in aiccu.conf.
This means that the service fails to start.
However, this is not a reason to completely break
apt-get upgrade|dist-upgrade.  Please continue if "invoke-rc.d start" fails
by using || true or a similar construct.

Also, please don't ask debconf questions for the username and password,
when these are trivially editable in the configuration file.  It serves
no purpose other than to annoy, because it interrupts upgrading by
requiring interactive prompting.  It's annoying because it's entirely
unnecessary and wastes everyone's time.  We have dpkg conffile
handling to deal with configuration file updates; please don't add
additional work on top of that.


Thanks,
Roger

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (550, 'unstable'), (500, 'testing'), (400, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aiccu depends on:
ii  debconf [debconf-2.0]  1.5.45
ii  iproute                20120521-3
ii  iputils-ping           3:20101006-1+b1
ii  iputils-tracepath      3:20101006-1+b1
ii  libc6                  2.13-34
ii  libgnutls26            2.12.20-1
ii  lsb-base               4.1+Debian7
ii  ucf                    3.0025+nmu3

Versions of packages aiccu recommends:
ii  bind9-host  1:9.8.1.dfsg.P1-4.1
ii  dnsutils    1:9.8.1.dfsg.P1-4.1
ii  ntp         1:4.2.6.p5+dfsg-2

aiccu suggests no packages.

-- Configuration Files:
/etc/aiccu.conf [Errno 13] Permission denied: u'/etc/aiccu.conf'

-- debconf information excluded



--- End Message ---
--- Begin Message ---
On 7/20/2012 9:52 AM, Reinier Haasjes wrote:
> I will leave this bug open for now if somebody want to comment on this,
> but I will close it in a few days.

As discussed above this only occurs when the user deliberately borkes
the config, in that case the upgrade should fail.

In all other scenarios the upgrade succeeds.

Regards,

Reinier

--- End Message ---

Reply via email to