[EPEL-devel] Re: Automatic python dependency generation on EPEL 8
> On 8/16/19 7:45 PM, Scott Talbert wrote: > > It seems to be working for me - not sure what the "official" stance is. Strange, it didn't seem to work here, for example: https://koji.fedoraproject.org/koji/buildinfo?buildID=1323057 ___ 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: Getting packages into EPEL-8
On 8/16/19 12:16 AM, willi.feh...@t-online.de wrote: Dear EPEL developers, I would like to request a handful of packages for EPEL-8. Name of the packages and short description and a reason why the package is needed. *Fail2Ban:* Fail2Ban is an Intrusion Prevention Software which protects systems from brute-force attacks. It's already available in EPEL-7 and it's actively used so I guess it make sense to push an .el8 package. This is on my incredibly long list of things to do. Any help is appreciated... -- 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
[EPEL-devel] Re: Automatic python dependency generation on EPEL 8
On 8/16/19 7:45 PM, Scott Talbert wrote: Is automatic python dependency generation supposed to work on EPEL 8? It seems to be working for me - not sure what the "official" stance is. -- 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
[EPEL-devel] Automatic python dependency generation on EPEL 8
Is automatic python dependency generation supposed to work on EPEL 8? ___ 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: Getting packages into EPEL-8
On Fri, 16 Aug 2019 at 02:17, willi.feh...@t-online.de wrote: > > Dear EPEL developers, > > > > I would like to request a handful of packages for EPEL-8. > > > > Name of the packages and short description and a reason why the package is > needed. > > > > Ansible: > Ansible is required for software provisioning and configuration management. > It's already available in EPEL-7 and it's actively used so I guess it make > sense to push an .el8 package. > This is being looked at. It may need to wait until RHEL-8.1 or .2 is released due to missing -devel packages it needs and thus may need to be a module. [Those items may not be needed so that is why I am saying it is being looked at.] > > Nagios Plugins: > There is already a Nagios Package in EPEL-8 but without having the Nagios > Plugins it's almost worthless to run Nagios. > Agreed. I got the first 2 in as testing of builds but ran into problems getting plugins compiled and ran out of time. It should be there soon. > -- 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?
Alright, the --skip-nvr-check makes it work. I don't need --target, although I have a package.cfg with it. It still gives a lot of error messages but then proceeds to build: Target epel8-playground is unknown. Skip. Could not find the release/dist from branch name epel8-playground Please specify with --release NVR checking will be skipped so I do not care that I am not able to construct NVR. I will refer this build by package name in following messages. Building singularity for epel8-playground-candidate ... Dave On Fri, Aug 16, 2019 at 08:59:33AM -0700, Troy Dawson wrote: > On Fri, Aug 16, 2019 at 7:18 AM Dave Dykstra wrote: > > > > So that did get the epel8-playground branch created for me, in this > > issue: > > https://pagure.io/releng/fedora-scm-requests/issue/15267 > > > > I was able to successfully pull the branch, populate it, and push it > > https://src.fedoraproject.org/rpms/singularity/tree/epel8-playground > > > > I tried first without a package.cfg and got these messages from fedpkg > > build: > > No local config file exists. > > Create package.cfg to specify build targets to build. > > Could not find the release/dist from branch name epel8-playground > > Please specify with --release > > Note: You can skip NVR construction & NVR check with --skip-nvr-check. > > See help for more info. > > Could not execute build: Cannot continue without properly constructed > > NVR. > > > > Ok, so I created a package.cfg with targets = epel8-playground and then > > fedpkg build gave me these messages: > > Target epel8-playground is unknown. Skip. > > Could not find the release/dist from branch name epel8-playground > > Please specify with --release > > Note: You can skip NVR construction & NVR check with --skip-nvr-check. > > See help for more info. > > Could not execute build: Cannot continue without properly constructed > > NVR. > > > > I tried using fedpkg --release epel8 build but that just moved it over > > to the epel8 branch; when used with --skip-nvr-check it said > > Building singularity-3.3.0-1.el8 for epel8-candidate > > Can you figure out what's still not right? > > > > Dave > > > > This is how I build for playground > > fedpkg build --skip-nvr-check --target=epel8-playground > > "skip-nvr-check" skips the initial check that fedpkg does to see if a > package has already been built. Although that is a nice thing to do, > koji also does a check, so it isn't completely necessary. > > "target=epel8-playground" I'm not positive this is necessary, but I > was using fedpkg back before it was patched to know about playground, > and that's just what I do right now. > > I believe fedpkg is going to be updated to do the nvr check correctly. > But the team is stretched fairly thin and they were working mainly on > "critical bugs" regarding playground. bugs that couldn't be worked > around with an option. > > Troy > > > On Thu, Aug 15, 2019 at 05:47:57PM -0500, Dave Dykstra wrote: > > > Troy, > > > > > > I did fedpkg request-branch epel8 and it did indeed make two issues. > > > Looking back at all issues that I previously had requested, last time it > > > only made one issues for epel8 and did not make the epel8-playground > > > issue. I wonder how many other people had or will have the same > > > problem. I assume this is going to fix the problem and if not I will > > > follow up. > > > > > > Thanks, > > > > > > Dave > > > > > > On Thu, Aug 15, 2019 at 06:25:41AM -0700, Troy Dawson wrote: > > > > That's not the error I was getting. I gave it a try also, and got the > > > > same error as you. > > > > > > > > I'd say, re-request the branches. When they try to re-make a branch > > > > that is already there, it will just say that the branch is already > > > > there, if it isn't, then it will make it. No real harm in > > > > re-requesting them. > > > > > > > > fedpkg request-branch epel8 > > > > > > > > But make sure that it does *two* issues. If there is only one issue, > > > > then something is wrong with your fedpkg. > > > > > > > > On Wed, Aug 14, 2019 at 3:25 PM Dave Dykstra wrote: > > > > > > > > > > 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
[EPEL-devel] Re: how to use epel8-playground?
On Fri, Aug 16, 2019 at 7:18 AM Dave Dykstra wrote: > > So that did get the epel8-playground branch created for me, in this > issue: > https://pagure.io/releng/fedora-scm-requests/issue/15267 > > I was able to successfully pull the branch, populate it, and push it > https://src.fedoraproject.org/rpms/singularity/tree/epel8-playground > > I tried first without a package.cfg and got these messages from fedpkg > build: > No local config file exists. > Create package.cfg to specify build targets to build. > Could not find the release/dist from branch name epel8-playground > Please specify with --release > Note: You can skip NVR construction & NVR check with --skip-nvr-check. > See help for more info. > Could not execute build: Cannot continue without properly constructed NVR. > > Ok, so I created a package.cfg with targets = epel8-playground and then > fedpkg build gave me these messages: > Target epel8-playground is unknown. Skip. > Could not find the release/dist from branch name epel8-playground > Please specify with --release > Note: You can skip NVR construction & NVR check with --skip-nvr-check. > See help for more info. > Could not execute build: Cannot continue without properly constructed NVR. > > I tried using fedpkg --release epel8 build but that just moved it over > to the epel8 branch; when used with --skip-nvr-check it said > Building singularity-3.3.0-1.el8 for epel8-candidate > Can you figure out what's still not right? > > Dave > This is how I build for playground fedpkg build --skip-nvr-check --target=epel8-playground "skip-nvr-check" skips the initial check that fedpkg does to see if a package has already been built. Although that is a nice thing to do, koji also does a check, so it isn't completely necessary. "target=epel8-playground" I'm not positive this is necessary, but I was using fedpkg back before it was patched to know about playground, and that's just what I do right now. I believe fedpkg is going to be updated to do the nvr check correctly. But the team is stretched fairly thin and they were working mainly on "critical bugs" regarding playground. bugs that couldn't be worked around with an option. Troy > On Thu, Aug 15, 2019 at 05:47:57PM -0500, Dave Dykstra wrote: > > Troy, > > > > I did fedpkg request-branch epel8 and it did indeed make two issues. > > Looking back at all issues that I previously had requested, last time it > > only made one issues for epel8 and did not make the epel8-playground > > issue. I wonder how many other people had or will have the same > > problem. I assume this is going to fix the problem and if not I will > > follow up. > > > > Thanks, > > > > Dave > > > > On Thu, Aug 15, 2019 at 06:25:41AM -0700, Troy Dawson wrote: > > > That's not the error I was getting. I gave it a try also, and got the > > > same error as you. > > > > > > I'd say, re-request the branches. When they try to re-make a branch > > > that is already there, it will just say that the branch is already > > > there, if it isn't, then it will make it. No real harm in > > > re-requesting them. > > > > > > fedpkg request-branch epel8 > > > > > > But make sure that it does *two* issues. If there is only one issue, > > > then something is wrong with your fedpkg. > > > > > > On Wed, Aug 14, 2019 at 3:25 PM Dave Dykstra wrote: > > > > > > > > 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 > > > >
[EPEL-devel] Re: 2 weeks in testing for new packages?
On Thu, 15 Aug 2019 at 21:12, Richard Shaw wrote: > > Does it make sense for packages to wait in testing for two weeks when they > are new packages? > Thanks for bringing this up. I was hoping to get this mentioned before FLOCK etc but we have been snowed under in Fedora Infrastructure. I would like for the developers and consumers to give some feedback on what they think are appropriate deadlines. The ones we have now are mostly inertia. > For example, all the packages I'm building for the first time in epel8... > > Even outside of new packages I rarely get karma for my Fedora packages, much > less for my EPEL packages and two weeks is a "long time". I have some > upstreams where I have to skip releases because they update within the two > week period and the policy of obsoleting an update when a new one is created > would mean they would perpetually be in testing and never make it to stable. > Would those upstreams make more sense in epel-playground only? Those go into the compose tree as soon as possible. > Perhaps it would be a good idea to let the maintainer determine if a previous > update should be obsoleted or not when pushing a new update? > > 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] Re: What to do about missing gcc-objc from RHEL8?
On Thu, 15 Aug 2019 at 12:17, Orion Poplawski wrote:
>
> What to do about missing gcc-objc from RHEL8? Are there alternative compilers
> yet that we can access? Will we have to package gcc-objc for EPEL8
> separately?
>
gcc-objc will need someone to make a module or SCL for it. The GCC
src.rpm seems to be patched out to not make any of the alternative
compilers that gcc normally makes. So someone will need to take this
on as a major project to form. I mention an SCL (or something similar)
because RHEL-8.x seems to be using scl's for updated compilers.
For a spitball-strawman, I would probably make a fully updated gcc
stack which compiled into /opt/epel/{bin,lib,etc} (I put in a ticket
for us to get this namespace reserved by the official Linux Filesystem
group last year. I have not heard anything for/against it so may just
say fudge it and use it). Again spitball
For a better strawman, this needs to be done in the CentOS-SCL and we
work out how to integrate our efforts somewhere.
Beyond that, anything from Red Hat will need to be done through the
customer process like Troy mentions.
> --
> 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] Re: how to use epel8-playground?
So that did get the epel8-playground branch created for me, in this issue: https://pagure.io/releng/fedora-scm-requests/issue/15267 I was able to successfully pull the branch, populate it, and push it https://src.fedoraproject.org/rpms/singularity/tree/epel8-playground I tried first without a package.cfg and got these messages from fedpkg build: No local config file exists. Create package.cfg to specify build targets to build. Could not find the release/dist from branch name epel8-playground Please specify with --release Note: You can skip NVR construction & NVR check with --skip-nvr-check. See help for more info. Could not execute build: Cannot continue without properly constructed NVR. Ok, so I created a package.cfg with targets = epel8-playground and then fedpkg build gave me these messages: Target epel8-playground is unknown. Skip. Could not find the release/dist from branch name epel8-playground Please specify with --release Note: You can skip NVR construction & NVR check with --skip-nvr-check. See help for more info. Could not execute build: Cannot continue without properly constructed NVR. I tried using fedpkg --release epel8 build but that just moved it over to the epel8 branch; when used with --skip-nvr-check it said Building singularity-3.3.0-1.el8 for epel8-candidate Can you figure out what's still not right? Dave On Thu, Aug 15, 2019 at 05:47:57PM -0500, Dave Dykstra wrote: > Troy, > > I did fedpkg request-branch epel8 and it did indeed make two issues. > Looking back at all issues that I previously had requested, last time it > only made one issues for epel8 and did not make the epel8-playground > issue. I wonder how many other people had or will have the same > problem. I assume this is going to fix the problem and if not I will > follow up. > > Thanks, > > Dave > > On Thu, Aug 15, 2019 at 06:25:41AM -0700, Troy Dawson wrote: > > That's not the error I was getting. I gave it a try also, and got the > > same error as you. > > > > I'd say, re-request the branches. When they try to re-make a branch > > that is already there, it will just say that the branch is already > > there, if it isn't, then it will make it. No real harm in > > re-requesting them. > > > > fedpkg request-branch epel8 > > > > But make sure that it does *two* issues. If there is only one issue, > > then something is wrong with your fedpkg. > > > > On Wed, Aug 14, 2019 at 3:25 PM Dave Dykstra wrote: > > > > > > 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 t
