New upstream bugfix release 1.0.4 (LXC MRE)

Bug #1329932 reported by Stéphane Graber
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

We have released LXC 1.0.4 upstream: https://linuxcontainers.org/news

This will be the first upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above.

The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html

As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now.

The packaging changes don't cause any change of behavior on the users' side but does allow for easier debugging in bug reports by allowing for cgmanager to be removed. Similarly the apparmor dependency change results in an identical dependency line on trusty, it's only been changed that way to make it possible to then backport the package as-is to all previous Ubuntu releases.

This upload is identical to that already in utopic.

Changed in lxc (Ubuntu):
status: New → Fix Released
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Stéphane, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/lxc/1.0.4-0ubuntu0.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 lxc (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Stéphane Graber (stgraber) wrote :

I've done a couple more testsuite runs with this version, it's also been in utopic for over a week now with no known regressions and I've been running it on 3 production servers running pretty complex setups for about as long, so I'm now marking this verification-done.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc - 1.0.4-0ubuntu0.1

---------------
lxc (1.0.4-0ubuntu0.1) trusty; urgency=medium

  * New upstream bugfix release. (MRE trackaging bug LP: #1329932)
    - Drop all existing patches (all applied upstream).
    - Fix lxc-attach failing from a different login session. (LP: #1315052)
    - Fix wrong cgroup on login to container. (LP: #1315521)

  * Cherry-pick upstream (stable branch) commits to fix testsuite under adt:
    - tests: Avoid the download template when possible
    - tests: Don't fail when HOME isn't defined
    - tests: apparmor: Always end with a newline

  * Sync packaging with utopic:
    - Depend on either cgmanager or cgroup-lite and recommend cgmanager.
      This should ensure systems get cgmanager by default even if cgroup-lite
      is already installed, yet makes it possible for the user to remove
      cgmanager if they really want to.
    - Remove hardcoded dependency on apparmor, instead generate it from
      rules so that the source package can be backported without changes (the
      right apparmor version will be picked up based on the release number).
    - Do not start lxc-instance in postinst without any instance specified,
      as that is an invalid request.
 -- Stephane Graber <email address hidden> Sat, 14 Jun 2014 20:09:57 -0400

Changed in lxc (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Stéphane Graber (stgraber) wrote : Update Released

The verification of the Stable Release Update for lxc 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.