Does collaborator status have permission to push updates?

[Andrew Bauer]

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.

[Mattia Verga]

Il 22/03/21 18:56, Andrew Bauer ha scritto:
>  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. 
Currently, Bodhi doesn't know what a collaborator is, so it will not
allow them to create / edit updates. It will in the next version, but
I'm not sure when it's going to be deployed (pretty sure it will not be
so soon because of the deployment of nogging and the following bugfixing
period - infra folks will have enough work).

For reference, see https://github.com/fedora-infra/bodhi/pull/4181

Mattia

[Andrew Bauer]

Understood. Thank you for the fast response.