On 8/14/19 6:40 PM, Stephen John Smoogen wrote:
On Wed, 14 Aug 2019 at 18:07, Orion Poplawski orion@nwra.com wrote:
I see virt modules (from dnf module info virt): 8000020190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 8000020190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 8000020190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 8000020190618154454 - libssh2-0:1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 820190226174025 - libssh2-0:1.8.0-7.module+el8+2833+c7d6d092
and virt-devel: 820190226174025: - libssh2-devel-0:1.8.0-7.module+el8+2833+c7d6d092
Seems to me like the EPEL8 builder is failing to pick up 820190226174025 virt module - possibly because the version does not sort higher than 8000020190618154454 ? Which seems perfectly understandable to me, but I have no idea how this is all supposed to work.
Okay, I see your point now - we're missing the 8000020190618154454 virt-devel module...
FWIW - I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1741362
Yeah the problem is that the 2 sets of modules have to match up for this work. We could try to keep the old one for building but I believe it has cve's in it. I think in the end I may just remove the virt-devel from the build system until they get it fixed as it is not helping in anyway.
This appears to be resolved now with the release of 8000020190828150510