#6156 Specifying groups in scm changes
Closed: Fixed 2 years ago Opened 5 years ago by orion.

https://fedoraproject.org/wiki/Package_SCM_admin_requests#Pseudo-users_and_Groups_for_SIGs indicates you can use group:: in owners. According to Jon Ciesla pkgdb complains about this. Does the wiki page need to be changed to have it in the initialcc field instead?


Which warnings does Jon get?

This should have been fixed and seems working last time I had a group:: in owners. Here the patches to the [https://git.fedorahosted.org/cgit/releng/commit/?id=75955f51627ff390511aabe3d01d84ca1efbf5d2 mailing list] and the [ https://git.fedorahosted.org/cgit/releng/commit/?id=75955f51627ff390511aabe3d01d84ca1efbf5d2 git repo].

It says something to the effect of groups cannot have ACL permissions. If I move the group:: to InitialCC it's fine.

Metadata Update from @orion:
- Issue set to the milestone: Fedora 22 Final

3 years ago

Metadata Update from @ausil:
- Issue close_status updated to: None
- Issue set to the milestone: Fedora 26 Alpha (was: Fedora 22 Final)
- Issue tagged with: meeting

3 years ago

Is this still an issue?

I haven't seen it in a long time, but we've also totally redone how this happens, so I'll open a new ticket if it comes back.

Metadata Update from @ausil:
- Issue untagged with: meeting

3 years ago

@pingou how will future plans impact this?

@ausil I don't know that it will, if you are referring to pagure groups will be able to get commit access to repo as happens on pagure.io

But reading the comments here, it seems that this ticket can be closed since @limb said he would re-open one if it happens again.

closing as there has been no activity. Please reopen if needed

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

2 years ago

Login to comment on this ticket.

Metadata