** Description changed: Binary package hint: lxc - Hello, + The LXC team would like the MIR team to reconsider promotion of LXC to + main. - I'd like lxc (userspace tools for the Linux Containers) to be moved to - main as was discussed in the specification and the session at the last - UDS: https://blueprints.launchpad.net/ubuntu/+spec/server-lucid- - contextualization + The reason is that since the last request back in Lucid, the kernel has had a lot of time to stabilize and improve for the various calls used by lxc. + We also added apparmor confinement by default a few cycles ago. - The package is currently in universe, was recently updated (0.6.3 to - 0.6.4), Debian relationship is good and the Debian maintainer is active. - Upstream is also very responsive (received answers to some question, a - few hours after I sent them), the project itself is mainly developed by - IBM France. + LXC is used by quite a lot of people and is the default backend for JuJu + charms development. - The reason for inclusion is that LXC is supported in the current Lucid - kernel, is considered a good alternative to the OpenVZ patch we used to - have in the previous LTS and Lucid's libvirt will support it. The lxc - tools aren't required if one wants to use libvirt, though it was - considered useful to have them in main nevertheless as some users don't - necessarily want to use libvirt to manage their containers. + Serge Hallyn and myself are active upstream contributors and maintainers of the staging branch, so issues tend to be resolved very quickly. + We've also been maintaining LXC in precise and quantal very actively, by SRUing every fix that lands in the development release and offering backports for more complex features. - There's currently no real bugs (outside wishlist) open on Launchpad, - Debian has two bug reports open that seem to be packaging related. There - is no known security issues (checked for CVE and secunia). + The staging LXC git tree is automatically imported on Launchpad and + daily builds for precise, quantal and raring are triggered + automatically. - Binary package only depends on the libc6, build-deps are "cdbs, - debhelper (>= 7), autotools-dev, libcap-dev, linux-libc-dev", so nothing - fancy or outside main here. + Upstream itself only contains a limited set of test, mostly around the + newly introduced liblxc API, however, Serge maintains a separate + integration testing branch which we run before upload and will be + integrated into autopkgtest and into the upstream dailies once we have + some time to do so. - I went through https://wiki.ubuntu.com/UbuntuMainInclusionRequirements - and everything seems to be ok with that package being moved to Main. + For build-depends: The only build-deps not currently in main is + libseccomp for which I'll be filing a separate MIR. LXC itself doesn't + strictly require this library but the feature is rather nice to have, so + I think we should get it promoted too. - Please feel free to ask for any additional information you may need. + I believe all the dependencies are already in main (outside of + libseccomp and lxc itself). + + LXC doesn't ship any daemon or setuid binary by default, some people + choose to mark some of the binaries as setuid or grant extra + capabilities, but we don't recommend doing so and don't do it by + default. + + The LXC package provides two upstart jobs, one to automatically start + containers at boot time (if marked as auto-started) and another to setup + a "lxcbr0" bridge with a dnsmasq DHCP server running on it, similar to + libvirt's virbr0.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/509647 Title: [MIR] lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/509647/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
