Re: [lago-devel] merge_repos is not picking the latest version of ioprocess?

The latest I'm interested in is 0.15.0-4.el7: mini@ykaul-mini:~/ovirt-system-tests$ find /var/lib/lago/reposync -name "ioprocess*.rpm" /var/lib/lago/reposync/ovirt-3.6-el7/x86_64/ioprocess-0.15.0-2.el7.x86_64.rpm /var/lib/lago/reposync/epel-el7/i/ioprocess-0.15.0-4.el7.x86_64.rpm /var/lib/lago/reposync/epel-el6/ioprocess-0.14.0-1.el6.x86_64.rpm /var/lib/lago/reposync/ovirt-3.6-el6/x86_64/ioprocess-0.15.0-2.el6.x86_64.rpm But merge picks 0.15.0-2.el7 instead: 2016-03-21 13:14:11,458::merge_repos.py::merge::123::ovirtlago.merge_repos::DEBUG::Copying /var/lib/lago/reposync/ovirt-3.6-el7/x86_64/ioprocess-0.15.0-2.el7.x86_64.rpm to output directory 2016-03-21 13:14:12,224::merge_repos.py::merge::123::ovirtlago.merge_repos::DEBUG::Copying /var/lib/lago/reposync/ovirt-3.6-el7/noarch/python-ioprocess-0.15.0-2.el7.noarch.rpm to output directory Which causes the VM to take the right one from EPEL directly (and not via the localsync). Thoughts?

_______________________________________________ lago-devel mailing list lago-devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/lago-devel