7:42 a.m.
$ fedpkg clone nuvola-app-mixcloud; cd nuvola-app-mixcloud
$ fedpkg import ~/rpmbuild/SRPMS/nuvola-app-mixcloud-3.2-3.fc26.src.rpm
$ git commit -m "Initial import (#1478067)."
$[martin@f26 nuvola-app-mixcloud]$ git push -v
Pushing to ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
FATAL: W any rpms/nuvola-app-mixcloud martinkg DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
8:35 a.m.
On Thu, Aug 10, 2017 at 12:42:26PM -0000, Martin Gansser wrote:
$ fedpkg clone nuvola-app-mixcloud; cd nuvola-app-mixcloud
$ fedpkg import ~/rpmbuild/SRPMS/nuvola-app-mixcloud-3.2-3.fc26.src.rpm
$ git commit -m "Initial import (#1478067)."
$[martin@f26 nuvola-app-mixcloud]$ git push -v
Pushing to ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
FATAL: W any rpms/nuvola-app-mixcloud martinkg DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
It looks like there was a glitch and the gitolite configuration file had not
been updated after Ralph created the project.
I've updated the configuration and I'm re-compiling it so in a few minutes this
should start working.
Sorry for the inconvenience,
Pierre
8:45 a.m.
On Thu, Aug 10, 2017 at 03:35:13PM +0200, Pierre-Yves Chibon wrote:
On Thu, Aug 10, 2017 at 12:42:26PM -0000, Martin Gansser wrote:
> $ fedpkg clone nuvola-app-mixcloud; cd nuvola-app-mixcloud
> $ fedpkg import ~/rpmbuild/SRPMS/nuvola-app-mixcloud-3.2-3.fc26.src.rpm
> $ git commit -m "Initial import (#1478067)."
>
> $[martin@f26 nuvola-app-mixcloud]$ git push -v
> Pushing to ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
> FATAL: W any rpms/nuvola-app-mixcloud martinkg DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: Could not read from remote repository.
It looks like there was a glitch and the gitolite configuration file had not
been updated after Ralph created the project.
I've updated the configuration and I'm re-compiling it so in a few minutes this
should start working.
You should be good now :)
Pierre
11:50 a.m.
ok git push works now, but ... unknown branches.
[martin@f26 nuvola-app-mixcloud]$ git push
Everything up-to-date
[martin@f26 nuvola-app-mixcloud]$ fedpkg build --nowait
/usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning:
fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead.
DeprecationWarning)
Building nuvola-app-mixcloud-3.2-3.fc27 for rawhide
Created task: 21149744
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=21149744
Result on koji:
BuildError: package nuvola-app-mixcloud not in list for tag f27-pending
and fo f26:
[martin@f26 nuvola-app-mixcloud]$ fedpkg switch-branch f26; git merge master; fedpkg push;
fedpkg build --nowait
/usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning:
fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead.
DeprecationWarning)
Could not execute switch_branch: Unknown remote branch origin/f26
and for f25:
[martin@f26 nuvola-app-mixcloud]$ fedpkg switch-branch f25; git merge master; fedpkg push;
fedpkg build --nowait
/usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning:
fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead.
DeprecationWarning)
Could not execute switch_branch: Unknown remote branch origin/f25
3:30 p.m.
Hi,
"Martin Gansser" <martin.gansser(a)gmail.com> writes:
ok git push works now, but ... unknown branches.
[...]
Result on koji:
BuildError: package nuvola-app-mixcloud not in list for tag f27-pending
I'm seeing a similar error now for uom-se and it's initial build.
Cheers,
Lukas
3:51 a.m.
In addition to new package not building because of tag, by following the
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Im...
On step:
fedpkg switch-branch BRANCH
Gives:
$ fedpkg switch-branch f26
/usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning:
fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead.
DeprecationWarning)
Could not execute switch_branch: Unknown remote branch origin/f26
Despise that branch have been approved, other branches seems that had been deleted somehow
in the process.
5:17 a.m.
for f27: This is a known problem see: https://pagure.io/fedora-infrastructure/issue/6236
They working on it right now.
f26 works for me now with:
$ git checkout -b f26; git push --set-upstream origin f26; fedpkg build --nowait
on f25 branch: I don't know what happens.
$ git push --set-upstream origin f25
Total 0 (delta 0), reused 0 (delta 0)
remote: FATAL: C refs/heads/f25 rpms/nuvola-app-mixcloud martinkg DENIED by
refs/heads/f[0-9][0-9]
remote: error: hook declined to update refs/heads/f25
To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
! [remote rejected] f25 -> f25 (hook declined)
error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud'
9:57 a.m.
On Fri, Aug 11, 2017 at 10:17:59AM -0000, Martin Gansser wrote:
for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
They working on it right now.
f26 works for me now with:
$ git checkout -b f26; git push --set-upstream origin f26; fedpkg build --nowait
on f25 branch: I don't know what happens.
$ git push --set-upstream origin f25
Total 0 (delta 0), reused 0 (delta 0)
remote: FATAL: C refs/heads/f25 rpms/nuvola-app-mixcloud martinkg DENIED by
refs/heads/f[0-9][0-9]
remote: error: hook declined to update refs/heads/f25
To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
! [remote rejected] f25 -> f25 (hook declined)
error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud'
Basically, in order to prevent people from creating an epel8 branches we only
apply the same restrictions as before (no fXX or elXX or epelXX or olpcXX
branches that are not whitelisted.
But the script that whitelist these branches but putting them into PDC doesn't
ask pagure to refresh its config, so PDC is up to date but not pagure, until
that project's config gets updated.
We're working on allowing the script run by the admin to trigger a refresh of
the config of a certain project so that right after creating the branch in pdc
it can ask pagure to refresh the corresponding config.
In the mean time admins have a way to manually ask that a projet be refreshed so
feel free to reach out if needed.
Sorry for the inconvenience,
Pierre
3:52 p.m.
On 08/11/2017 09:57 AM, Pierre-Yves Chibon wrote:
On Fri, Aug 11, 2017 at 10:17:59AM -0000, Martin Gansser wrote:
> for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
> They working on it right now.
>
> f26 works for me now with:
> $ git checkout -b f26; git push --set-upstream origin f26; fedpkg build --nowait
>
> on f25 branch: I don't know what happens.
>
> $ git push --set-upstream origin f25
> Total 0 (delta 0), reused 0 (delta 0)
> remote: FATAL: C refs/heads/f25 rpms/nuvola-app-mixcloud martinkg DENIED by
refs/heads/f[0-9][0-9]
> remote: error: hook declined to update refs/heads/f25
> To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
> ! [remote rejected] f25 -> f25 (hook declined)
> error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud'
Basically, in order to prevent people from creating an epel8 branches we only
apply the same restrictions as before (no fXX or elXX or epelXX or olpcXX
branches that are not whitelisted.
But the script that whitelist these branches but putting them into PDC doesn't
ask pagure to refresh its config, so PDC is up to date but not pagure, until
that project's config gets updated.
We're working on allowing the script run by the admin to trigger a refresh of
the config of a certain project so that right after creating the branch in pdc
it can ask pagure to refresh the corresponding config.
In the mean time admins have a way to manually ask that a projet be refreshed so
feel free to reach out if needed.
I'm getting a similar error when trying to create the epel7 branch for
tcl-tclnagios:
$ git push -v --set-upstream origin epel7
Pushing to ssh://wart@pkgs.fedoraproject.org/rpms/tcl-tclnagios
Total 0 (delta 0), reused 0 (delta 0)
remote: FATAL: C refs/heads/epel7 rpms/tcl-tclnagios wart DENIED by
refs/heads/epel[0-9]
remote: error: hook declined to update refs/heads/epel7
To ssh://wart@pkgs.fedoraproject.org/rpms/tcl-tclnagios
! [remote rejected] epel7 -> epel7 (hook declined)
error: failed to push some refs to
'ssh://wart@pkgs.fedoraproject.org/rpms/tcl-tclnagios'
Can I request a refresh?
--Wart
12:16 p.m.
On Fri, Aug 11, 2017 at 03:52:59PM -0500, Wart wrote:
On 08/11/2017 09:57 AM, Pierre-Yves Chibon wrote:
> On Fri, Aug 11, 2017 at 10:17:59AM -0000, Martin Gansser wrote:
>> for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
>> They working on it right now.
>>
>> f26 works for me now with:
>> $ git checkout -b f26; git push --set-upstream origin f26; fedpkg build
--nowait
>>
>> on f25 branch: I don't know what happens.
>>
>> $ git push --set-upstream origin f25
>> Total 0 (delta 0), reused 0 (delta 0)
>> remote: FATAL: C refs/heads/f25 rpms/nuvola-app-mixcloud martinkg DENIED by
refs/heads/f[0-9][0-9]
>> remote: error: hook declined to update refs/heads/f25
>> To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
>> ! [remote rejected] f25 -> f25 (hook declined)
>> error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud'
>
> Basically, in order to prevent people from creating an epel8 branches we only
> apply the same restrictions as before (no fXX or elXX or epelXX or olpcXX
> branches that are not whitelisted.
> But the script that whitelist these branches but putting them into PDC doesn't
> ask pagure to refresh its config, so PDC is up to date but not pagure, until
> that project's config gets updated.
>
> We're working on allowing the script run by the admin to trigger a refresh of
> the config of a certain project so that right after creating the branch in pdc
> it can ask pagure to refresh the corresponding config.
> In the mean time admins have a way to manually ask that a projet be refreshed so
> feel free to reach out if needed.
I'm getting a similar error when trying to create the epel7 branch for
tcl-tclnagios:
Refresh in progress, sorry for the delay.
Pierre
1:23 p.m.
2017-08-13 11:16 GMT-06:00 Pierre-Yves Chibon <pingou(a)pingoured.fr>:
On Fri, Aug 11, 2017 at 03:52:59PM -0500, Wart wrote:
> On 08/11/2017 09:57 AM, Pierre-Yves Chibon wrote:
> > On Fri, Aug 11, 2017 at 10:17:59AM -0000, Martin Gansser wrote:
> >> for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
> >> They working on it right now.
> >>
> >> f26 works for me now with:
> >> $ git checkout -b f26; git push --set-upstream origin f26; fedpkg build
--nowait
> >>
> >> on f25 branch: I don't know what happens.
> >>
> >> $ git push --set-upstream origin f25
> >> Total 0 (delta 0), reused 0 (delta 0)
> >> remote: FATAL: C refs/heads/f25 rpms/nuvola-app-mixcloud martinkg DENIED by
refs/heads/f[0-9][0-9]
> >> remote: error: hook declined to update refs/heads/f25
> >> To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud
> >> ! [remote rejected] f25 -> f25 (hook declined)
> >> error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-mixcloud'
> >
> > Basically, in order to prevent people from creating an epel8 branches we only
> > apply the same restrictions as before (no fXX or elXX or epelXX or olpcXX
> > branches that are not whitelisted.
> > But the script that whitelist these branches but putting them into PDC
doesn't
> > ask pagure to refresh its config, so PDC is up to date but not pagure, until
> > that project's config gets updated.
> >
> > We're working on allowing the script run by the admin to trigger a refresh
of
> > the config of a certain project so that right after creating the branch in pdc
> > it can ask pagure to refresh the corresponding config.
> > In the mean time admins have a way to manually ask that a projet be refreshed
so
> > feel free to reach out if needed.
>
> I'm getting a similar error when trying to create the epel7 branch for
> tcl-tclnagios:
Refresh in progress, sorry for the delay.
Worked! Thank for working on the
weekend.
Christoph
Pierre
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
--
Christoph Junghans
Web: http://www.compphys.de
12:48 p.m.
how long will it take until I can push new packages again for f26 and f25 ?
[martin@f26 nuvola-app-8tracks]$ git checkout -b f26; git push --set-upstream origin f26
Switched to a new branch 'f26'
Total 0 (delta 0), reused 0 (delta 0)
remote: FATAL: C refs/heads/f26 rpms/nuvola-app-8tracks martinkg DENIED by
refs/heads/f[0-9][0-9]
remote: error: hook declined to update refs/heads/f26
To ssh://pkgs.fedoraproject.org/rpms/nuvola-app-8tracks
! [remote rejected] f26 -> f26 (hook declined)
error: failed to push some refs to
'ssh://martinkg@pkgs.fedoraproject.org/rpms/nuvola-app-8tracks'
1:18 p.m.
i still get the message koji not in list errors, some works... some doesn't ...
BuildError: package nuvola-app-mixcloud not in list for tag f25-updates-candidate
BuildError: package nuvola-app-google-play-music not in list for tag
f26-updates-candidate
BuildError: package nuvola-app-google-play-music not in list for tag f25-updates-candidate
1:31 p.m.
On 08/16/2017 11:18 AM, Martin Gansser wrote:
i still get the message koji not in list errors, some works... some
doesn't ...
BuildError: package nuvola-app-mixcloud not in list for tag f25-updates-candidate
BuildError: package nuvola-app-google-play-music not in list for tag
f26-updates-candidate
BuildError: package nuvola-app-google-play-music not in list for tag
f25-updates-candidate
The script that syncs this got stuck this morning. :(
It's running again now... it takes about 30min or so to run, so things
should be all updated after that.
Additionally, we are replacing this script with one that listens to
fedmsgs and on new branches just adds those, so hopefully after today
they should get added right after the branch.
The slow script will still run once a day to make sure no requests were
dropped.
kevin
2:18 a.m.
On Wed, 2017-08-16 at 11:31 -0700, Kevin Fenzi wrote:
On 08/16/2017 11:18 AM, Martin Gansser wrote:
> i still get the message koji not in list errors, some works... some
> doesn't ...
>
> BuildError: package nuvola-app-mixcloud not in list for tag f25-
> updates-candidate
> BuildError: package nuvola-app-google-play-music not in list for
> tag f26-updates-candidate
> BuildError: package nuvola-app-google-play-music not in list for
> tag f25-updates-candidate
The script that syncs this got stuck this morning. :(
It's running again now... it takes about 30min or so to run, so
things
should be all updated after that.
Additionally, we are replacing this script with one that listens to
fedmsgs and on new branches just adds those, so hopefully after today
they should get added right after the branch.
The slow script will still run once a day to make sure no requests
were
dropped.
kevin
I just forked fedpkg minutes ago when writing this mail. I also can't
push to my forked repo.
I got these fetch and push urls.
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(fetch)
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(push)
and got similar error reported originally in this thread,
FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
2:27 a.m.
On Thu, 2017-08-17 at 15:18 +0800, Chenxiong Qi wrote:
On Wed, 2017-08-16 at 11:31 -0700, Kevin Fenzi wrote:
> On 08/16/2017 11:18 AM, Martin Gansser wrote:
> > i still get the message koji not in list errors, some works...
> > some
> > doesn't ...
> >
> > BuildError: package nuvola-app-mixcloud not in list for tag f25-
> > updates-candidate
> > BuildError: package nuvola-app-google-play-music not in list for
> > tag f26-updates-candidate
> > BuildError: package nuvola-app-google-play-music not in list for
> > tag f25-updates-candidate
>
> The script that syncs this got stuck this morning. :(
>
> It's running again now... it takes about 30min or so to run, so
> things
> should be all updated after that.
>
> Additionally, we are replacing this script with one that listens to
> fedmsgs and on new branches just adds those, so hopefully after
> today
> they should get added right after the branch.
>
> The slow script will still run once a day to make sure no requests
> were
> dropped.
>
> kevin
>
I just forked fedpkg minutes ago when writing this mail. I also can't
push to my forked repo.
I got these fetch and push urls.
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(fetch)
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(push)
and got similar error reported originally in this thread,
FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
It works now. Thanks.
>
> >
> > _______________________________________________
> > devel mailing list -- devel(a)lists.fedoraproject.org
> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
10:10 a.m.
On Thu, Aug 17, 2017 at 03:18:54PM +0800, Chenxiong Qi wrote:
I just forked fedpkg minutes ago when writing this mail. I also
can't
push to my forked repo.
I got these fetch and push urls.
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(fetch)
mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
(push)
and got similar error reported originally in this thread,
FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I am getting the same error while trying to push to a repository created
this morning.
$ git push origin master
FATAL: W any rpms/golang-github-shogo82148-go-shuffle athoscr DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
--
Athos Ribeiro
http://www.ime.usp.br/~athoscr
10:17 a.m.
On Thu, Aug 17, 2017 at 12:10:04PM -0300, Athos Ribeiro wrote:
On Thu, Aug 17, 2017 at 03:18:54PM +0800, Chenxiong Qi wrote:
> I just forked fedpkg minutes ago when writing this mail. I also can't
> push to my forked repo.
>
> I got these fetch and push urls.
>
> mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
> (fetch)
> mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git
> (push)
>
> and got similar error reported originally in this thread,
>
> FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
I am getting the same error while trying to push to a repository created
this morning.
$ git push origin master
FATAL: W any rpms/golang-github-shogo82148-go-shuffle athoscr DENIED by fallthru
(or you mis-spelled the reponame)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Fix running, it looks like the tool processing the requests is still missing one
API call :)
Pierre
6:07 a.m.
for f27: This is a known problem see:
https://pagure.io/fedora-infrastructure/issue/6236
They working on it right now.
f26 works for me now with:
$ git checkout -b f26; git push --set-upstream origin f26; fedpkg build --nowait
Used your workaround, I can't build the package now in koji with a message:
BuildError: package hd-idle not in list for tag f26-updates-candidate
Same with other branches other then master.
2442
days inactive
2449
days old
18 comments
9 participants
participants (9)
-
Athos Ribeiro -
Chenxiong Qi -
Christoph Junghans -
Kevin Fenzi -
Lukas Berk -
Martin Gansser -
Pierre-Yves Chibon -
Samuel Rakitničan -
Wart