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
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
>
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
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
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
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
On Mon, 12 Aug 2019 at 17:47, 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*
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
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,
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
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.
Dave
On Tue, Aug 06, 2019 at 03:21:32PM -0400, Stephen John Smoogen wrote:
>
On Tue, 6 Aug 2019 at 15:10, Dave Dykstra wrote:
> I don't think I understand how epel8-playground is envisioned to be
> used. I did the fedpkg request-branch epel8 and got it created for my
> package. I also ran fedpkg request-branch epel8-playground as in the
> script below, but that was
12 matches
Mail list logo
