Hello, I can provide a log summing up the logs submitted by the LXC maintainers on the lxc-devel mainling list on the intermediate releases between 0.8 and 0.9.
They look something like this: > -----Original Message----- > From: Stéphane Graber [mailto:[email protected]] > Sent: Tuesday, April 02, 2013 4:39 AM > To: Daniel Lezcano > Cc: Lxc development list > Subject: [lxc-devel] LXC 0.9 final pull request > > Hi Daniel, > > You'll find the 0.9 pull request below. > > Based on what you did last time, the following should do the trick: > - Review the pull request > - Use "git pull --edit --no-ff --stat git://github.com/lxc/lxc.git", > that should do a real merge, letting you do a proper Sign-off of the > changes. > - Update the version number to 0.9 > - Commit and tag > > Feature changes include: > - Support for ephemeral containers in lxc-clone > - --clear-env/--keep-env support in lxc-attach > - -n option to lxc-start-ephemeral > > Everything else is bugfixes on top of rc1. > > > Before sending this pull request I've done the following tests: > - Test build on my machine (up to date Ubuntu 13.04) > - Test build on Launchpad (Ubuntu 12.04, 12.10 and 13.04) > - Test build on an armhf board running Ubuntu 13.04 > - Test build for Android cross-compiling on my laptop > - Ran our test suite on the x86 binaries > - Ran a quick test (start/stop/info/wait) on Android > - Tested the API and tools on ARM > - Rebuilt all my local templates (~20 containers) on a variety of > architectures (i386, amd64, armel and armhf) Is this ok? How should I submit the log? Best regards, Bogdan P. > -----Original Message----- > From: Bruce Ashfield [mailto:[email protected]] > Sent: Wednesday, April 10, 2013 3:53 PM > To: Purcareata Bogdan-B43198 > Cc: [email protected] > Subject: Re: [meta-virtualization] [PATCH] Add LXC 0.9.0 recipe > > Can we get a bit of a long log that describes how this was testing ? Or > an entry in the meta-virtualization/docs directory ? > > There's no reason to keep this the existing recipe around, so the 0.8.0 > recipe should be removed, and we can see the differences between the > two and ensure that functionality drops and adds are understood. > > Cheers, > > Bruce > > On Wed, Apr 10, 2013 at 5:50 AM, Bogdan Purcareata > <[email protected]> wrote: > > --- > > recipes-containers/lxc/lxc_0.9.0.bb | 38 > > +++++++++++++++++++++++++++++++++++++ > > 1 file changed, 38 insertions(+) > > create mode 100644 recipes-containers/lxc/lxc_0.9.0.bb > > > > diff --git a/recipes-containers/lxc/lxc_0.9.0.bb > > b/recipes-containers/lxc/lxc_0.9.0.bb > > new file mode 100644 > > index 0000000..292285d > > --- /dev/null > > +++ b/recipes-containers/lxc/lxc_0.9.0.bb > > @@ -0,0 +1,38 @@ > > +DESCRIPTION = "lxc aims to use these new functionnalities to provide an > > userspace container object" > > +SECTION = "console/utils" > > +LICENSE = "GPLv2" > > +LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c" > > +PRIORITY = "optional" > > +PR = "r1" > > +DEPENDS = "libxml2 libcap" > > +RDEPENDS_${PN} = " \ > > + rsync \ > > + gzip \ > > + libcap-bin \ > > + bridge-utils \ > > + dnsmasq \ > > + perl-module-strict \ > > + perl-module-getopt-long \ > > + perl-module-vars \ > > + perl-module-warnings-register \ > > + perl-module-exporter \ > > + perl-module-constant \ > > + perl-module-overload \ > > + perl-module-exporter-heavy \ > > +" > > + > > +SRC_URI = "http://lxc.sourceforge.net/download/lxc/${PN}-${PV}.tar.gz \ > > + " > > +SRC_URI[md5sum] = "8552a4479090616f4bc04d8473765fc9" > > +SRC_URI[sha256sum] = > > "1e1767eae6cc5fbf892c0e193d25da420ba19f2db203716c38f7cdea3b654120" > > + > > +S = "${WORKDIR}/${PN}-${PV}" > > + > > +PACKAGECONFIG ??= "" > > +PACKAGECONFIG[doc] = "--enable-doc,--disable-doc" > > +PACKAGECONFIG[rpath] = "--enable-rpath,--disable-rpath" > > +PACKAGECONFIG[apparmour] = > > "--enable-apparmor,--disable-apparmor,apparmor,apparmor" > > + > > +inherit autotools > > + > > +FILES_${PN}-dbg += "${libexecdir}/lxc/.debug" > > -- > > 1.7.11.7 > > > > > > _______________________________________________ > > meta-virtualization mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-virtualization > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
