procps will not install in multistrap unless upstart is running on the host system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
procps (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: procps
The postinst of procps starts the service using the upstart command 'start procps'. If upstart is not running it fails with "start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/
This is trivially fixed by appending || true to the start procps line in procps.postinst
This solution is already present in the udev postinst script
Examples of cases when this is practical problem:
If the package is being installed in a chroot created on a Debian system (or any other system not runnig upstart) then it fails to install, and stops other packages that depend on it from installing.
Currently using multistrap or debootstrap to create a maverick chroot on a Debian system falls over on this bug.
ProblemType: Bug
Architecture: amd64
Date: Wed Aug 18 11:25:01 2010
DistroRelease: Ubuntu 10.10
NonfreeKernelMo
Package: procps 1:3.2.8-9ubuntu3
ProcEnviron: PATH=(custom, no user)
SourcePackage: procps
Tags: maverick
Uname: Linux 2.6.32-trunk-amd64 x86_64
summary: |
- procps will not install in debootstrap or multistrap unless upstart is - running on the host system + procps will not install in multistrap unless upstart is running on the + host system |
tags: | added: patch |
Actually this problem does not affect debootstrap as that diverts the startup commands in the chroot to do nothing.