[libvirt] Entering freeze for libvirt 5.7.0
I'm a day late but I just tagged it in git and pushed signed tarball and source rpm to the usual place: https://libvirt.org/sources/ Seems to work fine in my very minimal testing, there is a few red spots in CI https://ci.centos.org/view/libvirt/ but they seems mostly related to Debian 10 testing so maybe there was a hiccup on that arch in CI... I guess I will push RC2 over the week-end, and if things are fine push the final 5.7.0 release next Tuesday, in the meantime, please give it some testing, thanks, Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
I have just tagged RC2 in git and pushed the signed tarball and source rpm to the usual place: https://libvirt.org/sources/ Seems fine in my minimal testing, there is two red spots in CI at CI https://ci.centos.org/view/libvirt/ but on different components than the ones for RC1 so I would assume some fuzzyness in Jenkins, not libvirt itself. Please give RC2 some testing, assuming everything looks fine Tuesday my evening I would then push 5.7.0 final, thanks, Daniel -- Daniel Veillard | Red Hat Developers Tools http://developer.redhat.com/ veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/
On 9/1/19 9:13 PM, Daniel Veillard wrote:
I have just tagged RC2 in git and pushed the signed tarball and source rpm to the usual place: https://libvirt.org/sources/
Sorry for raising this issue this late, but I found out only during weekend when I tried to build libvirt on my home machine. The build with --with-xenapi is broken: CC xenapi/libvirt_driver_xenapi_la-xenapi_driver.lo xenapi/xenapi_driver.c:38:10: fatal error: xen_common.h: No such file or directory #include "xen_common.h" ^~~~~~~~~~~~~~ compilation terminated. The commit that introduced this problem is ecc4d75d01 and reverting it solves the issue. Michal
On Sun, 2019-09-01 at 21:13 +0200, Daniel Veillard wrote:
I have just tagged RC2 in git and pushed the signed tarball and source rpm to the usual place: https://libvirt.org/sources/
Seems fine in my minimal testing, there is two red spots in CI at CI https://ci.centos.org/view/libvirt/ but on different components than the ones for RC1 so I would assume some fuzzyness in Jenkins, not libvirt itself.
The libosinfo issue looks entirely unrelated to libvirt, so we should be safe on that side. Not sure what to make of the virt-manager issue[1], as I'm not familiar enough with the project. Cole, Pavel? [1] https://ci.centos.org/view/libvirt/job/virt-manager-check/1054/systems=libvi... -- Andrea Bolognani / Red Hat / Virtualization
participants (3)
-
Andrea Bolognani -
Daniel Veillard -
Michal Privoznik