[Bug 1477051] Please test proposed package

Brian Murray brian at ubuntu.com
Wed Jul 22 15:49:52 UTC 2015


Hello Jean-Baptiste, or anyone else affected,

Accepted live-build into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/live-
build/3.0~a57-1ubuntu16.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to live-build in Ubuntu.
https://bugs.launchpad.net/bugs/1477051

Title:
  Phones on devel-proposed do not boot - /bin/sh: 1: /bin/sh: initctl:
  not found

Status in live-build package in Ubuntu:
  Confirmed
Status in live-build source package in Trusty:
  Fix Committed
Status in live-build source package in Vivid:
  Fix Committed

Bug description:
  [ SRU Justification ]
  There was a regression in the previous upload where, when upstart wasn't in the bootstrap set (which is generally true on vivid and wily), the final image would end up without /sbin/initctl

  [ Test Case ]
  Compare file lists on old and new images, make sure initctl is there again, and unpack the image to make sure it's the real binary from upstart, not a stub.

  [ Regression Potential ]
  If the logic is wrong, there could be cases where initctl doesn't exist, or is a stub.  See test case, make sure this isn't true. :P

  [ Original Report ]
  Phones on devel-proposed do not boot. Verified with devel-proposed/ubuntu/mako #263 and devel-proposed/meizu.en/arale #67

  logs in /var/log/upstart/ contain the following errors:

  ==> mountall.log <==
  mountall: Event failed

  ==> cgproxy.log <==
  /proc/self/fd/9: 2: /proc/self/fd/9: initctl: not found

  ==> cgmanager.log <==
  /bin/sh: 1: /bin/sh: initctl: not found
  /data/system-data/var/log/upstart # tail  mountall.log cgproxy.log cgmanager.log

  /data/system-data/var/log/upstart # tail  mountall.log cgproxy.log cgmanager.log
   boot-hooks-emit.log bluetooth-touch.log
  ==> mountall.log <==
  mountall: Event failed

  ==> cgproxy.log <==
  /proc/self/fd/9: 2: /proc/self/fd/9: initctl: not found

  ==> cgmanager.log <==
  /bin/sh: 1: /bin/sh: initctl: not found

  ==> boot-hooks-emit.log <==
  /proc/self/fd/9: 2: /proc/self/fd/9: initctl: not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1477051/+subscriptions



More information about the foundations-bugs mailing list