On Fri, 2012-07-06 at 00:42 +0200, Thibaut VARENE wrote: > title 680419 uptimed fails to configure on upgrade if config file is missing > severity 680419 normal > thanks > > On Thu, Jul 5, 2012 at 8:27 PM, Ian Campbell <[email protected]> wrote: > > Package: uptimed > > Version: 1:0.3.17-3.1 > > Severity: important > > > > Dear Maintainer, > > > > A recent upgrade attempt failed with: > > Preparing to replace uptimed 1:0.3.17-3 (using > > .../uptimed_1%3a0.3.17-3.1_amd64.deb) ... > > [...] > > Setting up uptimed (1:0.3.17-3.1) ... > > /var/lib/dpkg/info/uptimed.postinst: line 39: /etc/uptimed.conf: No > > such file or directory > > dpkg: error processing uptimed (--configure): > > subprocess installed post-installation script returned error exit > > status 1 > > > > and indeed I found that /etc/uptimed.conf did not exist. However I did > > have /etc/uptimed.conf.dpkg-old. I moved it to /etc/uptimed.conf and ran > > "dpkg > > --configure -a" which succeeded. Now I have: > > Hi > > I can't reproduce your bug unless I manually remove /etc/uptimed.conf > first.
I've certainly not moved the file to dpkg-old myself. > I don't know how much of a bug it is to have upgrade configure > fail on missing config file. A serious one. It leaves the package in an unconfigured state which took manual intervention to allow dpkg to complete. > Maybe it should fail gracefully. Of course it should! I can't believe you are even considering that it should not! > Nonetheless, it's possible to apt-get remove the package anyway and > install it back again afterwards. > > Since this is not a typical use case of the software and since it > doesn't affect the normal upgrade path, I'm downgrading this bug to > normal. > > Thanks > -- Ian Campbell You may get an opportunity for advancement today. Watch it!
signature.asc
Description: This is a digitally signed message part
