package runit 2.1.1-6.2ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

probably duplicate of bug 603934

It does not seem to be the case. I have the fixed upstart installed, and 'runit' still fails. So either bug 603934 is not really fixed, or this is a different thing:

[cerdea-aws]cerdea@xango3:~$ dpkg -l runit upstart
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============================================-==============================================-============================================================================================================
iF runit 2.1.1-6.2ubuntu1 system-wide service supervision
ii upstart 0.6.7-5 event-based init daemon
[cerdea-aws]cerdea@xango3:~$ sudo apt-get -f install
[sudo] password for cerdea:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up runit (2.1.1-6.2ubuntu1) ...
start: Job is already running: runsvdir
dpkg: error processing runit (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 runit
E: Sub-process /usr/bin/dpkg returned an error code (1)
[cerdea-aws]cerdea@xango3:~$

a quick chat with slangasek pointed to the issue: maintainer's scripts should call invoke-rc.d in lieu of calling upstart directly.

Given this package is not a critical one, I am downgrading severity to Medium.

If the problem is that upstart is used directly from the maintainer script, then this problem is also present in lucid, runit 2.0.0-1ubuntu4.

I'll check if changing the script solves the problem.

Just as a follow-up: My problem is caused by upstart not being able to handle chroots.

https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/430224

Getting the same issue on i386, was able to correct by installing version 2.1.1-4ubuntu1 instead

This bug is a regression from the 2.1.1-6.2ubuntu1 merge which I did in January. This bug came up due to a Debian change in NMU 6.2 which was not upstart-friendly.

Uploaded 2.1.1-6.2ubuntu2 with the fix. I tested the fix locally on my Natty box and it worked.

This bug was fixed in the package runit - 2.1.1-6.2ubuntu2

---------------
runit (2.1.1-6.2ubuntu2) natty; urgency=low

  * Load debconf libraries and purge its old configuration files before
    starting runsvdir so that the start command doesn't get called
    twice. (LP: #708579)
 -- Bilal Akhtar <email address hidden> Thu, 17 Mar 2011 17:43:56 +0300