[libvirt] ANNOUNCE: libvirt 0.9.11.3 maintenance release
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release. This release can be downloaded at: http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz List of changes since libvirt-0.9.11.2: * Stable release 0.9.11.3 * python: Fix doc directory name for stable releases * docs: Serialize running apibuild.py * configure: Use ustar format for dist tarball * qemu: improve errors related to offline domains * nwfilter: address more coverity findings * nwfilter: address coverity findings * util: fix error messages in virNetlinkEventServiceStart For info about past maintenance releases, see: http://wiki.libvirt.org/page/Maintenance_Releases Thanks, Cole
Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
List of changes since libvirt-0.9.11.2:
* Stable release 0.9.11.3 * python: Fix doc directory name for stable releases * docs: Serialize running apibuild.py * configure: Use ustar format for dist tarball * qemu: improve errors related to offline domains * nwfilter: address more coverity findings * nwfilter: address coverity findings * util: fix error messages in virNetlinkEventServiceStart
For info about past maintenance releases, see:
FYI, when configuring libvirt --with_hal and --without_ udev I'm seeing the following build failure Making all in src make[2]: Entering directory `/usr/src/packages/BUILD/libvirt-0.9.11.3/src' make[2]: *** No rule to make target `libvirt_dbus.syms', needed by `libvirt.syms'. Stop. It seems commit 372a14c6 should not have been backported to the stable branch without commit 2223ea98, but the latter doesn't look to be a bug fix and hence a target for the stable branch. BTW, thanks Cole for doing this. Amazingly, it aligns nicely with the upcoming openSUSE12.2 release. I'll be sure to point out any candidate backports resulting from bug reports against 0.9.11.x in openSUSE12.2. Regards, Jim
On 05/15/2012 03:28 PM, Jim Fehlig wrote:
FYI, when configuring libvirt --with_hal and --without_ udev I'm seeing the following build failure
Making all in src make[2]: Entering directory `/usr/src/packages/BUILD/libvirt-0.9.11.3/src' make[2]: *** No rule to make target `libvirt_dbus.syms', needed by `libvirt.syms'. Stop.
It seems commit 372a14c6 should not have been backported to the stable branch without commit 2223ea98, but the latter doesn't look to be a bug fix and hence a target for the stable branch.
I concur - let's revert commit 372a14c (the v0.9.11-maint cherry-pick of mainline 28ae4ff0) before building 0.9.11.4. It looks like there are several other patches floating around that would warrant a new build in the near future, such as the inability to run secure usbredir channels over SPICE (bug 821469). -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On 05/06/2012 12:26 PM, Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
List of changes since libvirt-0.9.11.2:
* Stable release 0.9.11.3 * python: Fix doc directory name for stable releases * docs: Serialize running apibuild.py * configure: Use ustar format for dist tarball * qemu: improve errors related to offline domains * nwfilter: address more coverity findings * nwfilter: address coverity findings * util: fix error messages in virNetlinkEventServiceStart
Cole, I noticed that you were inconsistent on whether you used 'git cherry-pick -x' when backporting patches, which makes it a bit harder to see which mainline patch corresponds to each backported patch. I'm wondering if we should enforce a branch checkin policy that requires either a cherry pick id or a special comment stating that a patch is maint-branch-only (in the latter category would be patches that bump the version number in configure.ac). -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On 05/16/2012 02:17 PM, Eric Blake wrote:
On 05/06/2012 12:26 PM, Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
List of changes since libvirt-0.9.11.2:
* Stable release 0.9.11.3 * python: Fix doc directory name for stable releases * docs: Serialize running apibuild.py * configure: Use ustar format for dist tarball * qemu: improve errors related to offline domains * nwfilter: address more coverity findings * nwfilter: address coverity findings * util: fix error messages in virNetlinkEventServiceStart
Cole, I noticed that you were inconsistent on whether you used 'git cherry-pick -x' when backporting patches, which makes it a bit harder to see which mainline patch corresponds to each backported patch. I'm wondering if we should enforce a branch checkin policy that requires either a cherry pick id or a special comment stating that a patch is maint-branch-only (in the latter category would be patches that bump the version number in configure.ac).
Hmm, indeed, I didn't use the -x switch at all, didn't know about it. The commits using that switch were from danpb's initial maint tree. I'll make sure to use that in the future. - Cole
On 05/06/2012 12:26 PM, Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
This is great for Fedora 17. But right now, there are still several open bugs for Fedora 16. Would anyone object to the creation of the v0.9.6-maint branch, which starts out with cherry-picks of the same infrastructure as 0.9.11-maint in order to prepare for an 0.9.6.1 release? I'm prepared to make the first round of patches if this sounds reasonable. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
On 05/16/2012 05:50 PM, Eric Blake wrote:
On 05/06/2012 12:26 PM, Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
This is great for Fedora 17. But right now, there are still several open bugs for Fedora 16. Would anyone object to the creation of the v0.9.6-maint branch, which starts out with cherry-picks of the same infrastructure as 0.9.11-maint in order to prepare for an 0.9.6.1 release? I'm prepared to make the first round of patches if this sounds reasonable.
That sounds great to me, I can't imagine others would object either. Thanks, Cole
On 05/16/2012 04:36 PM, Cole Robinson wrote:
On 05/16/2012 05:50 PM, Eric Blake wrote:
On 05/06/2012 12:26 PM, Cole Robinson wrote:
libvirt 0.9.11.3 maintenance release is now available (actually, available since April 27 but I neglected to send this mail). This is libvirt 0.9.11 with additional bugfixes that have accumulated upstream since the initial release.
This release can be downloaded at:
http://libvirt.org/sources/stable_updates/libvirt-0.9.11.3.tar.gz
This is great for Fedora 17. But right now, there are still several open bugs for Fedora 16. Would anyone object to the creation of the v0.9.6-maint branch, which starts out with cherry-picks of the same infrastructure as 0.9.11-maint in order to prepare for an 0.9.6.1 release? I'm prepared to make the first round of patches if this sounds reasonable.
That sounds great to me, I can't imagine others would object either.
I have now created the v0.9.6-maint branch, and synced it up to the point of the Fedora 0.9.6-6 build. I applied the 21 patches that have already been backported to F16, omitting Fedora-specific patches 15 (only affects Fedora) and 23 (a one-liner Fedora specific change instead of properly backporting upstream spec file changes). I then backported several additional patch to get a clean 'make distcheck' run, including a few patches from the v0.9.11-maint branch (note that I did _not_ cherry-pick every single patch from v0.9.11-maint, since some of those were patches to issues present in 0.9.11 but not even coded in 0.9.6). I did not check for any other patches that are worth backporting before cutting the 0.9.6.1 release; doing that would require reading through open Fedora F16 bugs to see what people have identified as backporting candidates. But at least this should be enough to help Cole get started on an F16 build. -- Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
participants (3)
-
Cole Robinson -
Eric Blake -
Jim Fehlig