[Bug 602896] Re: Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

[Steve Langasek]

Sorry for the late turnaround on this.  I was going to make a case for
getting this fixed post-RC on the grounds that it would break
debootstrap, but now I realize that debootstrap correctly diverts
/sbin/initctl when bootstrapping, in addition to start-stop-daemon - so
the impact does indeed appear to be low, since it seems recommended best
practices after setting up a chroot are to divert /sbin/initctl to
/bin/true anyway.

This is still a bug which we should correct for natty, but I think the
correct fix is to drop this line out of debian/postinst *entirely*, and
instead use dh_installinit's support for starting and stopping jobs,
which already knows how to do do this.  Kees, you appear to be the
author of this change; do you recall why you hard-coded a 'start'
command in procps postinst, rather than changing debian/rules to not
override dh_installinit's behavior in the first place?  I don't see
anything in the changelog that explains why we need to run the procps
job on package install, if Debian isn't doing it this way.

-- 
Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
https://bugs.launchpad.net/bugs/602896
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “procps” package in Ubuntu: Confirmed

Bug description:
Binary package hint: procps

# dpkg --configure -a
Setting up procps (1:3.2.8-9ubuntu3) ...
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 procps

Cause is not allowing propc start to fail in the postinst script. Patch attached.