-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
Testable
-
-
https://pagure.io/releng/issue/12296
- Describe the issue
It looks like there's some kind of sync issue with requesting dist-git branches.
These requests were denied:
- https://pagure.io/releng/fedora-scm-requests/issue/66202
- https://pagure.io/releng/fedora-scm-requests/issue/66209
However, @music *is* co-maintainer of the package through the rust-sig group.
A request made by me (the main admin) succeeded, so it's not this specific package that's weird:
https://pagure.io/releng/fedora-scm-requests/issue/66210
Myself, I was able to request an epel10 branch in the exact same situation a few days ago:
https://pagure.io/releng/fedora-scm-requests/issue/65678
I am not a direct co-maintainer of rust-autocfg, but only co-maintainer through the rust-sig group.
I'm not sure if this is specific to @music, but he's the most recent member of the rust-sig group, so I'm suspecting it's some kind of sync issue - as far as I know, requests for epel9 and epel10 branches are not handled differently, are they?
- When do you need this? (YYYY/MM/DD)
Soon would be good. I need help with branching things for epel10, and granting individual co-maintainer access to potentially hundreds of packages for no good reason does not scale.
- When is this no longer needed or useful? (YYYY/MM/DD)
N/A
- If we cannot complete your request, what is the impact?
More work for me when dealing with branching for epel10, and an ACL issue that remains lurking somewhere.