My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092 needed by libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64
On my RHEL8 VM:
# dnf repoquery --whatprovides 'libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092' libssh2-0:1.8.0-7.module+el8+2833+c7d6d092.x86_64
There appear to be 3 different libssh2 builds:
libssh2.x86_64 1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8.0.0+3075+09be6b65.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8+2833+c7d6d092 rhel-8-for-x86_64-appstream-rpms
Is it possible that an odd combination of them are ending up in the EPEL8 buildroot?
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
# dnf install libssh2-devel Updating Subscription Management repositories. Last metadata expiration check: 0:07:30 ago on Wed 14 Aug 2019 03:50:13 PM EDT. No match for argument: libssh2-devel
I've got Code Ready Builder enabled. Anything else needed?
repo id repo name status codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady Linux Builder for RHEL 8 x86_64 ( 1,497 epel Extra Packages for Enterprise Linux 8 - x86_64 310 epel-testing Extra Packages for Enterprise Linux 8 - Testing - x 202 rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64 - AppStream ( 5,739 rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPM 2,097 rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64 - Supplementa 20
On Wed, 14 Aug 2019 at 16:01, Orion Poplawski orion@nwra.com wrote:
My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092 needed by libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64
Argh. I thought they fixed this in RHEL. The problem is that they did not rebuild the virt-devel module so the version shipped in RHEL currently is
./RHEL-8-001/virt:rhel:8000020190618154454:f8e95b4e:x86_64/libssh2-1.8.0-7.module+el8.0.0.z+3418+a72cf898.1.x86_64.rpm
but the version they ship in CRB is:
./RHEL-8-001/virt-devel:rhel:820190226174025:9edba152:x86_64/libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64.rpm
This is a RHEL issue versus anything we can fix :/.
On my RHEL8 VM:
# dnf repoquery --whatprovides 'libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092' libssh2-0:1.8.0-7.module+el8+2833+c7d6d092.x86_64
There appear to be 3 different libssh2 builds:
libssh2.x86_64 1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8.0.0+3075+09be6b65.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8+2833+c7d6d092 rhel-8-for-x86_64-appstream-rpms
Is it possible that an odd combination of them are ending up in the EPEL8 buildroot?
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
That is because the version in your VM is seeing the newer libssh2.x86_64 and so there is no libssh2-devel for it to match up with.
# dnf install libssh2-devel Updating Subscription Management repositories. Last metadata expiration check: 0:07:30 ago on Wed 14 Aug 2019 03:50:13 PM EDT. No match for argument: libssh2-devel
I've got Code Ready Builder enabled. Anything else needed?
repo id repo name status codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady Linux Builder for RHEL 8 x86_64 ( 1,497 epel Extra Packages for Enterprise Linux 8
- x86_64 310
epel-testing Extra Packages for Enterprise Linux 8
- Testing - x 202
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64
- AppStream ( 5,739
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64
- BaseOS (RPM 2,097
rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64
- Supplementa 20
-- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject...
On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
On Wed, 14 Aug 2019 at 16:01, Orion Poplawski orion@nwra.com wrote:
My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092 needed by libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64
Argh. I thought they fixed this in RHEL. The problem is that they did not rebuild the virt-devel module so the version shipped in RHEL currently is
./RHEL-8-001/virt:rhel:8000020190618154454:f8e95b4e:x86_64/libssh2-1.8.0-7.module+el8.0.0.z+3418+a72cf898.1.x86_64.rpm
but the version they ship in CRB is:
./RHEL-8-001/virt-devel:rhel:820190226174025:9edba152:x86_64/libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64.rpm
This is a RHEL issue versus anything we can fix :/.
On my RHEL8 VM:
# dnf repoquery --whatprovides 'libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092' libssh2-0:1.8.0-7.module+el8+2833+c7d6d092.x86_64
There appear to be 3 different libssh2 builds:
libssh2.x86_64 1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8.0.0+3075+09be6b65.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8+2833+c7d6d092 rhel-8-for-x86_64-appstream-rpms
Is it possible that an odd combination of them are ending up in the EPEL8 buildroot?
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
That is because the version in your VM is seeing the newer libssh2.x86_64 and so there is no libssh2-devel for it to match up with.
# dnf install libssh2-devel Updating Subscription Management repositories. Last metadata expiration check: 0:07:30 ago on Wed 14 Aug 2019 03:50:13 PM EDT. No match for argument: libssh2-devel
I've got Code Ready Builder enabled. Anything else needed?
repo id repo name status codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady Linux Builder for RHEL 8 x86_64 ( 1,497 epel Extra Packages for Enterprise Linux 8
- x86_64 310
epel-testing Extra Packages for Enterprise Linux 8
- Testing - x 202
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64
- AppStream ( 5,739
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64
- BaseOS (RPM 2,097
rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64
- Supplementa 20
Hmm, I'm not entirely sure I grok this. After enabling the virt-devel module I was able to install libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092 just fine.
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.
On 8/14/19 3:26 PM, Orion Poplawski wrote:
On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
On Wed, 14 Aug 2019 at 16:01, Orion Poplawski orion@nwra.com wrote:
My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092 needed by libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64
Argh. I thought they fixed this in RHEL. The problem is that they did not rebuild the virt-devel module so the version shipped in RHEL currently is
./RHEL-8-001/virt:rhel:8000020190618154454:f8e95b4e:x86_64/libssh2-1.8.0-7.module+el8.0.0.z+3418+a72cf898.1.x86_64.rpm
but the version they ship in CRB is:
./RHEL-8-001/virt-devel:rhel:820190226174025:9edba152:x86_64/libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64.rpm
This is a RHEL issue versus anything we can fix :/.
On my RHEL8 VM:
# dnf repoquery --whatprovides 'libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092' libssh2-0:1.8.0-7.module+el8+2833+c7d6d092.x86_64
There appear to be 3 different libssh2 builds:
libssh2.x86_64 1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8.0.0+3075+09be6b65.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8+2833+c7d6d092 rhel-8-for-x86_64-appstream-rpms
Is it possible that an odd combination of them are ending up in the EPEL8 buildroot?
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
That is because the version in your VM is seeing the newer libssh2.x86_64 and so there is no libssh2-devel for it to match up with.
# dnf install libssh2-devel Updating Subscription Management repositories. Last metadata expiration check: 0:07:30 ago on Wed 14 Aug 2019 03:50:13 PM EDT. No match for argument: libssh2-devel
I've got Code Ready Builder enabled. Anything else needed?
repo id repo name status codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady Linux Builder for RHEL 8 x86_64 ( 1,497 epel Extra Packages for Enterprise Linux 8
- x86_64 310
epel-testing Extra Packages for Enterprise Linux 8
- Testing - x 202
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64
- AppStream ( 5,739
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64
- BaseOS (RPM 2,097
rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64
- Supplementa 20
Hmm, I'm not entirely sure I grok this. After enabling the virt-devel module I was able to install libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092 just fine.
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...
On 8/14/19 3:35 PM, Orion Poplawski wrote:
On 8/14/19 3:26 PM, Orion Poplawski wrote:
On 8/14/19 2:54 PM, Stephen John Smoogen wrote:
On Wed, 14 Aug 2019 at 16:01, Orion Poplawski orion@nwra.com wrote:
My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
DEBUG util.py:585: BUILDSTDERR: Error: DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests DEBUG util.py:585: BUILDSTDERR: - nothing provides libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092 needed by libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64
Argh. I thought they fixed this in RHEL. The problem is that they did not rebuild the virt-devel module so the version shipped in RHEL currently is
./RHEL-8-001/virt:rhel:8000020190618154454:f8e95b4e:x86_64/libssh2-1.8.0-7.module+el8.0.0.z+3418+a72cf898.1.x86_64.rpm
but the version they ship in CRB is:
./RHEL-8-001/virt-devel:rhel:820190226174025:9edba152:x86_64/libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092.x86_64.rpm
This is a RHEL issue versus anything we can fix :/.
On my RHEL8 VM:
# dnf repoquery --whatprovides 'libssh2(x86-64) = 1.8.0-7.module+el8+2833+c7d6d092' libssh2-0:1.8.0-7.module+el8+2833+c7d6d092.x86_64
There appear to be 3 different libssh2 builds:
libssh2.x86_64 1.8.0-7.module+el8.0.0.z+3418+a72cf898.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8.0.0+3075+09be6b65.1 rhel-8-for-x86_64-appstream-rpms libssh2.x86_64 1.8.0-7.module+el8+2833+c7d6d092 rhel-8-for-x86_64-appstream-rpms
Is it possible that an odd combination of them are ending up in the EPEL8 buildroot?
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
That is because the version in your VM is seeing the newer libssh2.x86_64 and so there is no libssh2-devel for it to match up with.
# dnf install libssh2-devel Updating Subscription Management repositories. Last metadata expiration check: 0:07:30 ago on Wed 14 Aug 2019 03:50:13 PM EDT. No match for argument: libssh2-devel
I've got Code Ready Builder enabled. Anything else needed?
repo id repo name status codeready-builder-for-rhel-8-x86_64-rpms Red Hat CodeReady Linux Builder for RHEL 8 x86_64 ( 1,497 epel Extra Packages for Enterprise Linux 8
- x86_64 310
epel-testing Extra Packages for Enterprise Linux 8
- Testing - x 202
rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64
- AppStream ( 5,739
rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64
- BaseOS (RPM 2,097
rhel-8-for-x86_64-supplementary-rpms Red Hat Enterprise Linux 8 for x86_64
- Supplementa 20
Hmm, I'm not entirely sure I grok this. After enabling the virt-devel module I was able to install libssh2-devel-1.8.0-7.module+el8+2833+c7d6d092 just fine.
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
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.
-- Stephen J Smoogen.
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
On Wed, Aug 14, 2019 at 10:01 PM Orion Poplawski orion@nwra.com wrote:
My zabbix40 build for epel8 failed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=37041678
[...]
The other odd thing is that I cannot install libssh2-devel on my RHEL8 vm because it does not appear to exist:
It does not. It is not included in the core crypto libraries. From the SSH libs only libssh is: https://access.redhat.com/articles/3655361#which-are-the-rhel-core-crypto-co...
If the application has an option to compile with libssh, try that one.
regards, Nikos
epel-devel@lists.fedoraproject.org