Hello dann, or anyone else affected,

Accepted procps into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:3.3.10-4ubuntu2.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!

** Changed in: procps (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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/1637300

Title:
  procps upgrades fail in a LXD container

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  Fix Committed
Status in procps package in Debian:
  Fix Released

Bug description:
  [Impact]
  procps cannot be upgraded - or even reinstalled - in an LXD container. This 
means we cannot deliver updates (like the pending fix for LP: #1637026 in 
xenial-proposed) w/o putting container users in a bad state that requires a 
container restart to resolve.

  [Test Case]
  $ lxc launch ubuntu:xenial procpstest
  Creating procpstest
  Starting procpstest
  $ lxc exec procpstest -- /bin/bash
  root@procpstest:~# apt --reinstall install procps
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 209 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 procps arm64 
2:3.3.10-4ubuntu2 [209 kB]
  Fetched 209 kB in 1s (113 kB/s)  
  (Reading database ... 25398 files and directories currently installed.)
  Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2_arm64.deb ...
  Unpacking procps (2:3.3.10-4ubuntu2) over (2:3.3.10-4ubuntu2) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for systemd (229-4ubuntu11) ...
  Setting up procps (2:3.3.10-4ubuntu2) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Job for systemd-sysctl.service failed because the control process exited with 
error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" 
for details.
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing package procps (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   procps
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  root@procpstest:~#

  [Regression Risk]
  The proposed fix is to disable invoking the procps initscript on 
install/upgrade. This fix is already in yakkety, and I didn't find any bugs 
related to it in LP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637300/+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

Reply via email to