Hello William, or anyone else affected, Accepted procps into utopic-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/procps/1:3.3.9-1ubuntu5.2 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 Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1419554 Title: Can't upgrade procps in LXC 1.1 Status in procps package in Ubuntu: Fix Committed Status in procps source package in Precise: Fix Committed Status in procps source package in Trusty: Fix Committed Status in procps source package in Utopic: Fix Committed Status in procps source package in Vivid: Fix Committed Bug description: == SRU == Rationale: sysctl now fails with current LXC as files which shouldn't be written to in containers are read-only. A previous fix applied to the EACCESS case as returned by apparmor. Text case: start procps Regression potential: All EROFS write failures will now be ignored (an error is still logged) but I can't think of a case where that'd be a bad thing. Original bug report: LXC 1.1 on vivid has started giving privileged containers a read-only /sys, which prevents Ubuntu's procps Upstart job from starting. This isn't normally too problematic, except that the weekend's procps SRU's postinst tries to start the job and causes the upgrade to fail. Disabling the procps postinst makes apt usable again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1419554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
