On Wed, Dec 21, 2016 at 10:17 AM, Sandro Bonazzola <sbona...@redhat.com> wrote: > 00:00:31.874 Num Packages in Repos: 22534 > 00:00:31.875 package: > ovirt-provider-ovn-1.0-1.20161219125609.git.el7.centos.noarch from > check-custom-el7 > 00:00:31.876 unresolved deps: > 00:00:31.876 python-openvswitch >= 0:2.6 > 00:00:31.876 openvswitch-ovn-central >= 0:2.6 > 00:00:31.876 package: > ovirt-provider-ovn-driver-1.0-1.20161219125609.git.el7.centos.noarch from
It's good we have repoclosure, as it reminded us we cannot ship ovirt-provider-ovn unless we build and ship a version of openvswitch from from their master branch, at least until they ship ovs-2.7. Sandro, Marcin: can we do it? Can we supply our own build of openvswitch, like we did for Marcin's blog? > check-custom-el7 > 00:00:31.876 unresolved deps: > 00:00:31.876 python-openvswitch >= 0:2.6 > 00:00:31.876 openvswitch-ovn-host >= 0:2.6 > 00:00:31.877 openvswitch >= 0:2.6 > 00:00:31.877 package: > vdsm-gluster-4.18.999-1162.gite9544ovirt-provider-ovn2e.el7.centos.noarch from > check-custom-el7 > 00:00:31.877 unresolved deps: > 00:00:31.877 vdsm = 0:4.18.999-1162.gite95442e.el7.centos All of these seem like repoclosure false warning. After all, vdsm = 0:4.18.999-1162.gite95442e.el7.centos is the exact version of vdsm that is in the repo, right? _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
