Liviu: While chrooted, you probably don't want to start any services.
I suggest creating an executable /usr/sbin/policy-rc.d containing
simply exit 101. That will make invoke-rc.d refuse to start or stop
services. Remove this again before trying to boot the system.
--
You received this bug
On Fri, Sep 7, 2012 at 2:21 PM, Stefano Rivera launch...@rivera.za.net wrote:
Liviu: While chrooted, you probably don't want to start any services.
I suggest creating an executable /usr/sbin/policy-rc.d containing
simply exit 101. That will make invoke-rc.d refuse to start or stop
services.
Hello
I've encountered this issue while upgrading from Lucid to Precise. That means
that the issue is likely still present in Precise.
The upgrade process botched and now I can operate Ubuntu only from a chroot
environment. (For the discussion on the ML see [1].) The first error that
arises
This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached
end-of-life and is no longer supported, so I am closing the bugtask for
Maverick. Please upgrade to a newer version of Ubuntu.
More information here:
https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html
LGTM
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/602896
Title:
Fails to update in pbuilder: start: Unable to connect to
Hello Stefano, or anyone else affected,
Accepted procps into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
The SRU for bug #771372 shows that this bug is still a problem in
maverick: the installer diverts initctl when initially bootstrapping the
base system, but for some reason when it comes time to apply any package
updates (such as from -updates or -proposed), initctl is no longer
diverted, which
Steve, Kees, could one of you get that uploaded?
--
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
** Branch linked: lp:ubuntu/procps
--
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
Bugs, which is
** Changed in: procps (Ubuntu)
Assignee: (unassigned) = Kees Cook (kees)
** Changed in: procps (Ubuntu)
Milestone: None = natty-alpha-2
** Also affects: procps (Ubuntu Natty)
Importance: Low
Assignee: Kees Cook (kees)
Status: Confirmed
** Changed in: procps (Ubuntu
This bug was fixed in the package procps - 1:3.2.8-9ubuntu4
---
procps (1:3.2.8-9ubuntu4) natty; urgency=low
* debian/postinst, debian/rules: instead of manually calling 'start' in
the postinst, allow dh_installinit to DTRT. LP: #602896.
* debian/sysctl.d/README: fix the
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
I think this patch is the correct fix.
** Patch added: procps-602896.diff
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/602896/+attachment/1665095/+files/procps-602896.diff
--
Fails to update in pbuilder: start: Unable to connect to Upstart: Failed to
connect to socket
Sorry, it's lost to history. The debdiff looks correct to me. Thanks for
catching and fixing this!
--
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
The real bug here is that procps is calling 'start' from the maintainer
script at all. 'start' is not a standardized maintainer script
interface; we should be calling 'invoke-rc.d' instead for all services,
including those with upstart jobs. If this were fixed, I believe
pbuilder uses an
we should be calling 'invoke-rc.d' instead for all services, including
those with upstart jobs.
That makes sense. I'd assumed that it wasn't used for upstart jobs
because every upstartified package I've seen doesn't use it.
** Patch added: procps_3.2.8-9ubuntu4-take2.debdiff
MIght as well do my own debdiff, (why didn't I do it ages ago)?
** Patch added: procps_3.2.8-9ubuntu4.debdiff
https://bugs.edge.launchpad.net/ubuntu/+source/procps/+bug/602896/+attachment/1588073/+files/procps_3.2.8-9ubuntu4.debdiff
** Changed in: procps (Ubuntu)
Status: Incomplete =
dh, please use your real name in the changelog stanza instead of your
nick (nobled).
--
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
** Changed in: procps (Ubuntu)
Status: Confirmed = Incomplete
--
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
** Changed in: procps (Ubuntu)
Status: New = Confirmed
--
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
Yeah, developing/testing with pbuilder is pretty much impossible because
of this bug.
I put the patch into debdiff format if that makes it easier to sponsor.
** Patch added: Stefano's patch as a debdiff
http://launchpadlibrarian.net/52177704/procps-lp602896.debdiff
--
Fails to update in
** Patch added: procps-postinst-start.patch
http://launchpadlibrarian.net/51541216/procps-postinst-start.patch
** Description changed:
Binary package hint: procps
# dpkg --configure -a
Setting up procps (1:3.2.8-9ubuntu3) ...
start: Unable to connect to Upstart: Failed to connect
22 matches
Mail list logo
