[FFe] LXC 1.0~alpha1 in saucy

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

Bug Description

Hello,

I'd like to request a Freeze Exception for LXC 1.0~alpha1 to be uploaded to saucy as soon as it's actually released upstream.

Saucy currently ships LXC 0.9 with a dozen of cherry-picks for various bug fixes and features from LXC 1.0.
As Ubuntu 14.04 LTS will be shipping LXC 1.0 stable, we'd like to have 13.10 ship to something as close as possible to that to maximize exposure to some of the new code.

The major changes that happened so far in LXC 1.0 upstream are:
 - Rebasing of the various commands on the LXC API (dropping various shell scripts and switching to C equivalents)
 - New implementation of container cloning and snapshotting
 - Overlayfs clones of regular containers
 - Improved console handling (including SIGWINCH handling on lxc-start console)
 - Cleaner backing store support directly in LXC core
 - Support for building with current Android NDK
 - Quite a lot of additions to the LXC API and its bindings
 - Initial work towards unprivileged LXC containers
 - Improved stability with respect to threaded callers
 - The usual set of templates improvements and bug fixes

The LXC git branch is currently built for Ubuntu 12.04, 12.10, 13.04 and 13.10 on amd64 and i386, as well as armhf for 13.10 and against the Android NDK. Serge and I, as well as possibly a dozen more people are using those packages daily, so we're pretty confident that upstream git is stable and that 1.0~alpha1 is suitable for saucy.

Currently two products ship with LXC by default, Edubuntu (used by arkose) and Ubuntu Touch (used for the android container).
I'm the point of contact for both of those use cases and will test 1.0~alpha1 on those two products prior to uploading to the archive.

description: updated
Revision history for this message
Iain Lane (laney) wrote :

Will it be bug fix after the alpha?

Revision history for this message
Stéphane Graber (stgraber) wrote :

Yes, once we get the alpha in the archive, the only changes we'll be cherry-picking from upstream will be bug fixes.

Revision history for this message
Iain Lane (laney) wrote :

OK. Ack. Please go ahead.

Changed in lxc (Ubuntu):
status: New → Confirmed
Revision history for this message
Stéphane Graber (stgraber) wrote :

Thanks for approving the FFe.

Just a quick status update on this, I sent out the pull request for 1.0~alpha1 on Tuesday and we're now just waiting for Daniel to tag the release on sourceforge before I can upload this to the archive. I still have hope this may happen this week.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxc - 1.0.0~alpha1-0ubuntu2

---------------
lxc (1.0.0~alpha1-0ubuntu2) saucy; urgency=low

  * Add allow-stderr to autopkgtst restrictions as the Ubuntu template
    uses policy-rc.d to disable some daemons and that causes a message to
    be printed on stderr when the service tries to start.
 -- Stephane Graber <email address hidden> Thu, 12 Sep 2013 13:57:17 -0400

Changed in lxc (Ubuntu):
status: Confirmed → Fix Released
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.