[EPEL-devel] Re: EPEL 8 not finding buildroot overrides
Here's the link... https://bodhi.fedoraproject.org/overrides/hdf5-1.10.5-3.el8 Which is showing as active. Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
On Wed, 14 Aug 2019 at 18:07, Orion Poplawski wrote: > >> I see virt modules (from dnf module info virt): > >> 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > >> 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > >> 820190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > >> 820190618154454 - 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 > >> 820190618154454 ? 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 820190618154454 > > 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. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: how to use epel8-playground?
Hi Troy! I created my branch for singularity from epel8, but that wouldn't make a difference, would it? When I do fedpkg push from epel8-playground I get Current branch cannot be pushed anywhere! Counting objects: 5, done. Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 327 bytes | 0 bytes/s, done. Total 3 (delta 1), reused 0 (delta 0) remote: Unspecified ref refs/heads/epel8-playground is blocked remote: Denied push for ref 'refs/heads/epel8-playground' for user 'dwd' remote: All changes have been rejected To ssh://d...@pkgs.fedoraproject.org/rpms/singularity.git ! [remote rejected] HEAD -> epel8-playground (pre-receive hook declined) error: failed to push some refs to 'ssh://d...@pkgs.fedoraproject.org/rpms/singularity.git' Could not execute push: Failed to execute command. Dave On Mon, Aug 12, 2019 at 02:47:08PM -0700, Troy Dawson wrote: > Looks like you need at least fedpkg-1.37-3.el7 for it to work with the > playground stuff, so you should be good. > When I did the branches for KDE (about 350 of them) there were 6 that > didn't properly branch to epel8-playground. > They *said* they were branched, but they weren't. > I was able to push and create a branch though, because everything else > was setup. > > fedpkg switch-branch f30 > git checkout -b epel8-playground > fedpkg push > > I did f30 instead of master because that's the version we wanted for > KDE. You can do that from master if you want. > > Troy > > On Mon, Aug 12, 2019 at 2:17 PM Dave Dykstra wrote: > > > > Hi Kevin, > > > > I have fedpkg-1.37-4.el7, the latest version. My yum log shows I > > updated it from 1.37-2 on August 6 an hour and a half before I started > > this thread. If I recall correctly I saw an instruction somewhere that > > said to update it, and I did that before my initial attempt. > > > > Dave > > > > On Sun, Aug 11, 2019 at 10:01:47AM -0700, Kevin Fenzi wrote: > > > On 8/8/19 11:40 AM, Dave Dykstra wrote: > > > > Stephen, > > > > > > > > The package is singularity. > > > > > > > > The term "branch" in this context is not very clear to me. All I know > > > > is that there's no git branch on > > > > pkgs.fedoraproject.org/rpms/singularity; > > > > I don't know about other systems. > > > > > > What version of fedpkg do you have there? > > > > > > It might be the version is too old to understand the epel8-playground > > > request? > > > > > > kevin > > > > > > > > > > > > > > > > > ___ > > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > > To unsubscribe send an email to epel-devel-le...@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.org > > > > > ___ > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > To unsubscribe send an email to epel-devel-le...@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.org > > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@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.org > ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
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 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:820190618154454: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_64310 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-rpmsRed 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 - Supplementa20 >> >> >> 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): >> 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 >> 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 >> 820190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 >> 820190618154454 - 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 >> 820190618154454 ? 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 820190618154454 virt-devel > module... FWIW - I've filed https://bugzilla.redhat.com/show_bug.cgi?id=1741362 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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:
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
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 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:820190618154454: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_64310 >>> 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-rpmsRed 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 >>> - Supplementa20 > > > 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): > 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > 820190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 > 820190618154454 - 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 > 820190618154454 ? 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 820190618154454 virt-devel module... -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
On 8/14/19 2:54 PM, Stephen John Smoogen wrote: > On Wed, 14 Aug 2019 at 16:01, Orion Poplawski 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:820190618154454: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_64310 >> 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-rpmsRed 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 >> - Supplementa20 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): 820190510171727 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190516125745 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190529063309 - libssh2-0:1.8.0-7.module+el8.0.0+3075+09be6b65.1 820190618154454 - 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 820190618154454 ? Which seems perfectly understandable to me, but I have no idea how this is all supposed to work. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: libssh2 issues in EPEL8 buildroot
On Wed, 14 Aug 2019 at 16:01, Orion Poplawski 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:820190618154454: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_64310 > 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-rpmsRed 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 > - Supplementa20 > > > -- > Orion Poplawski > Manager of NWRA Technical Systems 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@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-le...@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.org -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] libssh2 issues in EPEL8 buildroot
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_64310 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-rpmsRed 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 - Supplementa20 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Announcing EPEL-8.0 Release
The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen, Robert Scheck, and many others in the community who helped in the last 6 months to get this release done. EPEL-8.0 has packages for the x86_64, ppc64le, aarch64, and now the s390x platforms. ## What is EPEL? EPEL stands for Extra Packages for Enterprise Linux and is a subcommunity of the Fedora and CentOS projects aimed at bringing a subset of packages out of Fedora releases ready to be used and installed on various Red Hat Enterprise Linux (RHEL). It is not a complete rebuild of Fedora or even of previous EPEL releases. EPEL is also a community and not a product. As such we need community members to help get packages into the repository more than done in Fedora. If you are interested in getting a package into EPEL, contact the package maintainer through bugzilla. This way the request can be tracked, and if the primary maintainer is not interested in branching to EPEL, others can step in and do so. Optionally you can send a request to the epel-devel@lists.fedoraproject.org mailing list. If you do so, please include why the package is needed, to help other volunteers decide whether they can support it. ## What is new? ### Playground for Rawhide like things We have added an additional set of channels for EPEL-8 called playground. It is similar to Fedora Rawhide so packagers can work on versions of software that are too fast moving or will have large API changes compared to versions in the regular channel. To make this purpose transparent, when a package is built in epel8, it will normally also be built in epel8-playground. This is done via a packages.cfg file which lists the targets for fedpkg to build against. A successful package build will then go through two different paths: * epel8 package will go into bodhi to be put into epel8-testing * epel8-playground will bypass bodhi and go directly into epel8-playground the next compose. If a packager needs to focus only on epel8 or epel8-playground they can edit packages.cfg to change the target=epel8 epel8-playground to target=epel8. Packages in epel8-playground are intended to be used in the following manner: * To test out a new version of the package that might not be stable yet. * To test out new packaging of the package * To test a major version change of the package intended for the next EPEL-8 minor release. * To build a package that will never be stable enough for EPEL-8, but still could be useful to some. At minor RHEL releases (ie, 8.1, 8.2) people can pull in big changes from playground to the main EPEL-8 packages. Since people will be upgrading and paying more attention than usual anyhow at those points, it’s a great chance to do that change, but you can test beforehand in the playground to make sure these changes work. Consumers should be aware that packages in EPEL8-playground are without any Service Level Expectations. You may want to only cherry pick packages from the playground as needed. ### New Architecture: s390x We have added the s390x platform to builds. Some consumers have wanted this platform for many years but we did not have the time to integrate necessary changes. We have done this with EPEL-8, and hope to be able to do so for EPEL-7 if there are continued requests for it. ## What is next? (Why is it called EPEL-8.0?) The goal for EPEL-8.1 will be implementing modules into the repository, which allows builds for packages that depend on non-shipped devel packages. It also allows maintainers to supplement and replace other packages they could not under standard EPEL rules. ## Known Issues: 1. EPEL-8.0 does not come with modules. Packages built for perl, python and other modules are only built against “default” modules. For example installing a perl library from EPEL will work with the perl-5.26 but not with the perl-5.24 module. 2. RHEL-8.0 and RHEL-8.1 beta do not come with the same packages in all architectures. There are 720 ‘desktop’ packages which were only shipped for x86_64 and ppc64le. Packagers looking to deliver GNOME, KDE, or other platforms will need to exclude s390x and aarch64 at this time. 3. The dnf in RHEL-8.1 beta does not work with the EPEL repository due to zchunk code. This has been opened as an upstream bug as https://bugzilla.redhat.com/show_bug.cgi?id=1719830 4. Until modularity and module builds are implemented in EPEL, there will be many packages which can not be built for EPEL. This is mainly due to RHEL-8 not shipping many -devel packages and the need for us to rebuild those packages in a module to make those -devel available to build against. When running into this please open a ticket with https://pagure.io/epel/new_issue for us to put in a request for it to be added to Red Hat’s Code Ready Builder.
[EPEL-devel] Re: EPEL 8 not finding buildroot overrides
On Wed, Aug 14, 2019 at 6:39 AM Troy Dawson wrote: > > On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote: > > > > > > > > On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: > >> > >> I have hdf5 (amongst others) in a buildroot override but when I tried to > >> build OpenImageIO I got the following errors in root.log: > >> > > Where is the link to that override? > I'm not seeing hdf5 in any overrides, but maybe I searched wrong. > All I see is this https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-70dbc966dd which is not an override, it is an update. As an update, it just stays in -testing, and doesn't go into the -build repo until it is done testing and pushed to stable. > >> DEBUG util.py:585: BUILDSTDERR: No matching package to install: > >> 'hdf5-devel' > >> > >> I'm I missing something? > >> > >> Ok, as I write this and investigate more it get's weirder... > >> > >> https://koji.fedoraproject.org/koji/buildinfo?buildID=1348296 > >> Shows the good build... > >> > >> $ koji wait-repo epel8-build --build=hdf5-1.10.5-3.el8 > >> Warning: package hdf5 is not in tag epel8-build > >> > >> It's technically in epel8-testing, but should that matter? I was > >> "collecting" builds into an update so I didn't forget all the ones that > >> needed to be pushed together. > >> > >> I guess I shouldn't have done that? > >> > > > > I am not sure. That sounds like the right thing, but I am not sure. > > > > > >> > >> Thanks, > >> Richard > >> ___ > >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org > >> To unsubscribe send an email to epel-devel-le...@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.org > > > > > > > > -- > > Stephen J Smoogen. > > > > ___ > > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > > To unsubscribe send an email to epel-devel-le...@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.org ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: EPEL 8 not finding buildroot overrides
On Wed, Aug 14, 2019 at 6:36 AM Stephen John Smoogen wrote: > > > > On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: >> >> I have hdf5 (amongst others) in a buildroot override but when I tried to >> build OpenImageIO I got the following errors in root.log: >> Where is the link to that override? I'm not seeing hdf5 in any overrides, but maybe I searched wrong. >> DEBUG util.py:585: BUILDSTDERR: No matching package to install: 'hdf5-devel' >> >> I'm I missing something? >> >> Ok, as I write this and investigate more it get's weirder... >> >> https://koji.fedoraproject.org/koji/buildinfo?buildID=1348296 >> Shows the good build... >> >> $ koji wait-repo epel8-build --build=hdf5-1.10.5-3.el8 >> Warning: package hdf5 is not in tag epel8-build >> >> It's technically in epel8-testing, but should that matter? I was >> "collecting" builds into an update so I didn't forget all the ones that >> needed to be pushed together. >> >> I guess I shouldn't have done that? >> > > I am not sure. That sounds like the right thing, but I am not sure. > > >> >> Thanks, >> Richard >> ___ >> epel-devel mailing list -- epel-devel@lists.fedoraproject.org >> To unsubscribe send an email to epel-devel-le...@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.org > > > > -- > Stephen J Smoogen. > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@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.org ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
[EPEL-devel] Re: EPEL 8 not finding buildroot overrides
On Tue, 13 Aug 2019 at 23:36, Richard Shaw wrote: > I have hdf5 (amongst others) in a buildroot override but when I tried to > build OpenImageIO I got the following errors in root.log: > > DEBUG util.py:585: BUILDSTDERR: No matching package to install: > 'hdf5-devel' > > I'm I missing something? > > Ok, as I write this and investigate more it get's weirder... > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1348296 > Shows the good build... > > $ koji wait-repo epel8-build --build=hdf5-1.10.5-3.el8 > Warning: package hdf5 is not in tag epel8-build > > It's technically in epel8-testing, but should that matter? I was > "collecting" builds into an update so I didn't forget all the ones that > needed to be pushed together. > > I guess I shouldn't have done that? > > I am not sure. That sounds like the right thing, but I am not sure. > Thanks, > Richard > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@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.org > -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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.org
