#8278 create caddy group
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by carlwgeorge.

The upstream maintainer of caddy would like to start offering the latest version of caddy for all branches in copr, under the caddy namespace. Per the FAQ item about groups in copr, I would like to request a FAS caddy group, with myself as a member (and others later of course).

https://docs.pagure.org/copr.copr/user_documentation.html#how-can-i-create-new-group


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

4 years ago

This worked great and I have the copr setup up now.

https://copr.fedorainfracloud.org/coprs/g/caddy/caddy/

I do have one follow up question. I would like to grant this group access to the Fedora caddy package as well, similar to how I have done for the go-sig group.

https://src.fedoraproject.org/rpms/caddy

When I try, the caddy group is not available in the list. Comparing the caddy and go-sig groups, these two things jump out at me:

  • Group type:
    • caddy is tracking
    • go-sig is pkgdb
  • Prerequisite:
    • caddy is cla_done
    • go-sig is packager

Should I change either (or both) of these so that I can grant the caddy group access to the Fedora caddy package?

Sorry, those are different types of groups and that won't work at all. ;(

We may be able to modify the caddy group into a pkgdb one, but the convention with those is $name-sig normally. Could we make a new caddy-sig group? or did you want us to try and convert caddy?

@pingou ^ thoughts?

Technically the -sig is no longer a requirement but it's the convention we've used so far, I kind of like it but we can of course re-visit it.

I don't know if we can easily change the group type but for the pre-requisite field, it'll have to be packager as only packagers can have access to packages in dist-git (ie: do not change the go-sig group which is correctly configured! :)).

Login to comment on this ticket.

Metadata