SRU of LXCFS 2.0.2 (upstream bugfix release)

Bug #1597493 reported by Stéphane Graber on 2016-06-29
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxcfs (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Unassigned
Xenial
Undecided
Unassigned

Bug Description

LXCFS upstream released LXC 2.0.2 as a bugfix release with following changelog:
 - Don't build pam/ when --with-pamdir=none
 - libpam_cgfs: Don't create new path if we are under /user.slice/user-$uid.slice

Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes.

Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support.

This bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression.

This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere.

Changed in lxcfs (Ubuntu):
status: New → Fix Released

Hello Stéphane, or anyone else affected,

Accepted lxcfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/2.0.2-0ubuntu1~ubuntu16.04.1 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 lxcfs (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed
Changed in lxcfs (Ubuntu Trusty):
status: New → Fix Released
Stéphane Graber (stgraber) wrote :

I've had this running for the past few days on a few servers, no problem found and we haven't received any negative feedback from yakkety, PPA or backports users either.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxcfs - 2.0.2-0ubuntu1~ubuntu16.04.1

---------------
lxcfs (2.0.2-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.2) (LP: #1597493):
    - Don't build pam/ when --with-pamdir=none
    - libpam_cgfs: Don't create new path if we are under
      /user.slice/user-$uid.slice
  * Update packaging to match Yakkety and Debian (no user visible change).

 -- Stéphane Graber <email address hidden> Wed, 29 Jun 2016 14:48:56 -0400

Changed in lxcfs (Ubuntu Xenial):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for lxcfs 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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers