[ovirt-devel] Re: OST broken - looks like https://gerrit.ovirt.org/c/99717 is the reason

Hi, there's one issue with 'python2-enum34' - it's an 'epel' package. I don't know if it's going to land in 'base' repository, but until then I think we should rely on 'python-enum34'. On 5/2/19 6:41 PM, Nir Soffer wrote: Acually everything worked fine in our 'check-install'. If you take a look at a test patch I've made: https://gerrit.ovirt.org/#/c/99809/ You can see that we install 'python2-enum34' when building artifacts with 'yum-builddep' because it's a build dependency - that's the reason it's not listed as a requirement when installing built 'vdsm-*' packages - it's already there. Both 'rpm -q python2-enum34' and 'repoquery -i python2-enum34' succeed - they show 'python2-enum34's origin as 'epel-el7'. We could make OST work by adding 'python2-enum34' to 'pkgs.txt' and rebuilding repository files, but I think we shouldn't for the reason I stated above - we should not depend on 'epel' packages. Regards, Marcin