On Thursday, June 23, 2022 6:25:00 AM CDT Nico Kadel-Garcia wrote:
Whoever is working with that right now is welcome to my notes and
tools, at
https://github.com/nkadel/ansiblerepo/
I have glanced at it before. @kevin and I maintain ansible, ansible-core, and
many of the standalone collection packages in Fedora.
EPEL 8 or EPEL 9 would probably benefit from my list of associated
python38 RPMs to satisfy the other ansible-core requirements, such as
the python38-resolvelib update and python38-pbr.
Note that ansible-core and python38-resolvelib are part of RHEL so we cannot
provide them in EPEL. EPEL packages are *Extra* Packages for Enterprise Linux.
However, we could definitely use help with packaging the surrounding packages
for python38 on RHEL 8 :).
I've tried before to
assemble the credentials and permissions to build EPEL packages
myself, but have been balked so far by the variety of registration
requirements. I'm willing to put those in myself if I can get some
walkthrough help getting the permissions together. Or I'm happy to
work with someone with EPEL and/or Fedora privileges to get these
published, and I'm not insistent on credit. Any takers?
Take a look at
https://docs.fedoraproject.org/en-US/package-maintainers/
Joining_the_Package_Maintainers/ and
https://docs.fedoraproject.org/en-US/
fesco/Packager_sponsor_policy/ . Usually, python38 compat packages for EPEL 8
are exempt from the review process if they're already packaged in Fedora, but
I don't see why you couldn't submit one for review in order to join the
packager group. There are other ways to join the packager group (see the
linked docs), but submitting a package review is the most common.
Also, note that there's no separate permissions for EPEL and Fedora Linux.
EPEL packagers are Fedora packagers.
--
Thanks,
Maxwell G (@gotmax23)
Pronouns: He/Him/His