On Fri, Aug 16, 2019 at 7:18 AM Dave Dykstra <dwd@xxxxxxxx> 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 <dwd@xxxxxxxx> 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://dwd@xxxxxxxxxxxxxxxxxxxxxx/rpms/singularity.git > > > > ! [remote rejected] HEAD -> epel8-playground (pre-receive hook declined) > > > > error: failed to push some refs to 'ssh://dwd@xxxxxxxxxxxxxxxxxxxxxx/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 <dwd@xxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxx > > > > > > > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > > > > 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@xxxxxxxxxxxxxxxxxxxxxxx > > > > > > _______________________________________________ > > > > > > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > > > > > > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > > > 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@xxxxxxxxxxxxxxxxxxxxxxx > > > > > _______________________________________________ > > > > > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > > > > > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > > 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@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
