python-hatch-requirements-txt is a stalled EPEL package. Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-package-request/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time. https://bugzilla.redhat.com/show_bug.cgi?id=2345138 This package is part of the mkdocs dependency stack. I am a member of the mkdocs-sig and I am requesting mkdocs-sig be given commit permissions so that I, or a member of the SIG, might branch and build this package in epel10. Thanks!
Metadata Update from @patrikp: - Issue assigned to patrikp
mkdocs-sig now has commit permissions in the repository. :thumbsup:
mkdocs-sig
https://src.fedoraproject.org/rpms/python-hatch-requirements-txt
Metadata Update from @patrikp: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I was able to request the branch, but I don't seem to be able to push to it:
$ git push Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) remote: Fall-through deny remote: Denied push for ref 'refs/heads/epel10' for user 'dcavalca' remote: All changes have been rejected To ssh://pkgs.fedoraproject.org/rpms/python-hatch-requirements-txt ! [remote rejected] epel10 -> epel10 (pre-receive hook declined) error: failed to push some refs to 'ssh://pkgs.fedoraproject.org/rpms/python-hatch-requirements-txt'
Metadata Update from @dcavalca: - Issue status updated to: Open (was: Closed)
@dcavalca Please do not branch epel packages without assuming responsibility.
@patrikp Please make @dcavalca the EPEL point of contact.
Yes, the idea is that mkdocs-sig would assume responsibility for EPEL for this package, like we've done for others in this stack. I would happily update it myself but only the main admin can.
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
You would want 'collaborator' for epel* then no?
Yes, that works.
@dcavalca You are now a collaborator for epel*. :thumbsup:
Log in to comment on this ticket.