Il 19/08/2014 13:08, Dan Kenigsberg ha scritto:
On Mon, Aug 18, 2014 at 03:15:21PM +0200, Sandro Bonazzola wrote:
Hi, looks like a patch have been merged causing repository closure breakage for VDSM on Fedora 19:
Yes, we are talking about
sparsify: integrating virt-sparsify into vdsm
package: vdsm-4.16.0-204.gitbf3d2b5.fc19.x86_64 from check-custom-fc19 unresolved deps: libguestfs-tools-c >= 1:1.26.7-2 package: vdsm-4.16.0-206.gitdd70c9e.fc19.x86_64 from check-custom-fc19 unresolved deps: libguestfs-tools-c >= 1:1.26.7-2
Since master is now targeted to oVirt 3.6.0 it may be a good point for deciding if we're going to keep support for Fedora 19 or not for the upcoming oVirt 3.6.0 planning.
For reference, Fedora 21 is expected to be released on 2014-11-11 [1], this means Fedora 19 is expected to go End Of Life on 2014-12-11 (one month later F21 release)[2].
I suggest to start provisioning some slaves with Fedora 21 and move master jobs currently running on F19 to F21.
Yes, please. The master branch was conciously broken on Fedora 19 (and el6.5) since we want this new features on master. el6.6 is going to have virt-sparsify, but f19 would not. So please, let us start deprecating f19 slaves. ovirt-3.6 won't support it as a valid platform.
In order to drop Fedora 19 from master, the following projects need to be branched for 3.5.z: - vdsm-jsonrpc-java - ovirt-reports - ovirt-dwh The following projects may probably not need to be branched but please take a look: - ioprocess - unboundid-ldapsdk I guess we can wait until 3.5.0 will be released before start changing.
[1] http://fedoraproject.org/wiki/Releases/21/Schedule [2] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedul...
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com