Does collaborator status have permission to push updates?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I was recently granted collaborator status for the pmount package.
https://src.fedoraproject.org/rpms/pmount

I did the usual. I requested the epel8 branch then built the package:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1726469

However, when I use fedpkg to push an update I get:
>$ fedpkg update
>Password: 
>Could not execute update: Could not generate update request: 
>A copy of the filled in template is saved as bodhi.template.last

I get a more helpful error message when I try to create an update in the Bodhi web portal:
> Builds : kni does not have commit access to pmount

It seems strange that I have permission to build the package, but not push it to Bodhi.

The various permission group definitions described on src.fedoraproect.org (ticket, collaborator, commit, admin) do not mention what is need to push an update. 

Can someone confirm whether this is indeed a permission problem or something else? Thank you.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux