desktop-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

> Of course I can create a $CHROOT/usr/sbin/policy-rc.d script
> to instruct invoke-rc.d to not try to start services when inside
> a chroot, but should I have to manually do that?

Yes, you should.  Just as you need to do so to stop non-upstart-managed
services from starting in a chroot.

** Changed in: upstart (Ubuntu)
       Status: New => Invalid

** Changed in: apport (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/727785

Title:
  apport fails to be configured in chroots

Status in “apport” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: apport

  Similar to LP bug #707971, but the fix there doesn't cover the case of
  chroots.

  While trying to `apt-get dist-upgrade` a Natty chroot, apport failed to be configured, along with all the packages that depend on it. The problem was the `invoke-rc.d apport start || exit $?` line added in apport.postinst by dh_installinit.
  I experienced the problem both with /$CHROOT/proc mounted and unmounted.

  Of course I can create a $CHROOT/usr/sbin/policy-rc.d script to
  instruct invoke-rc.d to not try to start services when inside a
  chroot, but should I have to manually do that?

  # dpkg-query -W apport upstart
  apport	1.19-0ubuntu1
  upstart	0.9.0-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/727785/+subscriptions