Hi, I am in favor of tagging e.g. the commit introducing the hook in question [1] with v4.16.99. (Similarly, in the message to ovirt-users [2] I suggested that anyone interested in the hook tag their master branch with "v4.17-fake".) I think that the tag v4.17 is very similar to the eventual tag v4.17.0 and might be confusing or sounding like a "hack"; but they are different tags nonetheless so I am not opposed to this solution either. Introducing the tag would make installing the hook painless to both groups (those on v4.16.7; and those on master, i.e., post-v4.16.0). [1] hooks: Add a hook to configure IPv6 networking through custom properties e42c9f3e9a2a4f759a66f11b3572d21c2b28d7c6 [2] IPv6 configuration through custom network properties and vdsm-hook-ipv6 ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; To: devel(a)ovirt.org, "infra" <infra(a)ovirt.org&gt; Sent: Thursday, November 6, 2014 8:25:09 AM Subject: [ovirt-devel] [ACTION REQUIRED] vdsm_master_install-rpm-sanity-el6_created bugged and vdsm spec file broken Looking at: http://jenkins.ovirt.org/job/vdsm_master_install-rpm-sanity-el6_created/5... The job is trying to install the src.rpm and fails: 16:45:09 Cannot add package /tmp/vdsm-4.16.0-501.gitf981b80.el6.src.rpm to transaction. Not a compatible architecture: src 16:45:11 Cannot add package /tmp/vdsm-4.16.0-501.gitf981b80.fc20.src.rpm to transaction. Not a compatible architecture: src After that, some rpms fails the install: Package: vdsm-hook-ipv6-4.16.0-501.gitf981b80.el6.noarch (/vdsm-hook-ipv6-4.16.0-501.gitf981b80.el6.noarch) 16:45:34 Requires: vdsm >= 4.16.7 Master must bump version to 4.16.99 or 4.17 or something like that in order to be installable. Last thing: Cents 6.6 now deliver glusterfs 3.6.0.28 and vdsm is explicitly requiring 3.5.2. Anything preventing to move to >= 3.5.2 instead of = 3.5.2? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel