The verification of the Stable Release Update for procps has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- 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 Released Status in procps source package in Precise: Fix Released Status in procps source package in Trusty: Fix Released Status in procps source package in Utopic: Fix Released Status in procps source package in Vivid: Fix Released 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
