#360 Please add "cockpit" user to packagers group
Closed: declined Opened by martinpitt.

The cockpit user is driven by
Cockpituous to automatically release the Cockpit Fedora package into koji and bodhi. For that it is a maintainer with commit access.

I would like to use this bot to release the sister project cockpit-ostree. I currently cannot do this on the Settings page:

This user must be in one of the following groups to be allowed to be added to this project: packager

So I suppose it isn't because this got set up for cockpit itself before the Pagure era. Can you please add it to that group, as it factually has been a maintainer for several years already?


https://admin.fedoraproject.org/accounts/user/view/cockpit shows that cockpit is already member of various groups. Dunno, did you try the usual solution of logging out and back in (using the cockpit user account)?

@cockpit is already member of packager group.
Date Approved: 2015-09-17 14:29:17 CEST
Sponsor: @sgallagh

Metadata Update from @mizdebsk:
- Issue assigned to mizdebsk
- Issue close_status updated to: declined
- Issue status updated to: Closed (was: Open)

Metadata Update from @martinpitt:
- Issue status updated to: Open (was: Closed)

https://src.fedoraproject.org/user/cockpit clearly shows "Groups: 0", while my own user https://src.fedoraproject.org/user/martinpitt shows "Groups: 1 [Packagers]".

Not sure if https://pagure.io/user/cockpit is any different, but it shows exactly the same here. And I still can't add it to https://src.fedoraproject.org/rpms/cockpit-ostree/settings .

Thus reopening.

Yes, but src.fp.o has just a cached copy of the permissions. The authoritative source is the accounts database, which shows that cockpit is a member of 'packager' group. So the problem is not how to change the group membership (this is already done), but how to teach src.fp.o about the membership. The membership is updated when a user logs in. Can you log in as the cockpit user in the web interface?

If I log in as "cockpit" user, I indeed can see the "packager" group, so this is somehow "private"?

But indeed logging out and back in did the trick (sorry, I missed @zbyszek 's first response). Thanks!

Metadata Update from @martinpitt:
- Issue close_status updated to: declined
- Issue status updated to: Closed (was: Open)

Metadata