#9710 db-sig group cannot be assigned access to components
Closed: Fixed by smooge. Opened by hhorak.

Describe what you would like us to do:


I'd like to ask for assistance or explanation for this problem. I'm trying to allow @db-sig group to be assigned in pagure, so all members of this group can have access to some of the components. This group is not in the list when I try to "Add group" for a component I'm owner for, like https://src.fedoraproject.org/container/perl/addgroup.

I suspect it can be related to the group type, which is currently "tracking" but there is also a value "pkgdb". However, I didn't find it explained anywhere. Any hints? Do I ask for a valid thing?

When do you need this to be done by?


not in hurry


I don't see this group in https://src.fedoraproject.org/groups.

I'm not seeing the ticket requesting this group to be created here. Do you have it?

It's a fas group created long time ago. Maybe I should not mix pagure and fas groups?

There are a set of requirements for dist-git groups https://pagure.io/fedora-infra/howtos/blob/master/f/groups_in_fedora.md

So you can't assume FAS groups == dist-git groups.

I see the point, but the link is broken for me -- Page not found (404).

Ah old url from my browser: https://pagure.io/fedora-infra/howtos/blob/main/f/groups_in_fedora.md

Thanks, it helped, but the text does not mention (unless I missed it) whether a group can have more than one type. We're using it as tracking already, can we add pkgdb to that? Or do we need a new group?

Thanks for the suggestion, groups can only have one type.

Ok, got it, feel free to close this unless you want to use it to track the slight text improvement (adding a note that only one group is possible). Thanks for a quick help!

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

we will be moving to a new system which will need all new docs

Metadata