EPEL Package Request

When requesting a Fedora package for EPEL, the steps are a little different depending on your ability or willingness to help.

Starting Point

The first step is to search to see if there is already a bugzilla bug requesting your package be added to EPEL. A search such a this usually will show and requests https://bugzilla.redhat.com/buglist.cgi?bug_status=open&component=nedit Be sure to change "nedit" to whatever package you are asking for.

If there are no requests, then you should open a bug on bugzilla requesting the package. https://bugzilla.redhat.com/enter_bug.cgi

  • Classification : Fedora

  • Product : "Fedora EPEL"

    • If <package> isn’t found in Component, the go back and for Product select "Fedora"

  • Component : <package>

  • Version : epel9 (or whatever epel version you want it it)

    • If using Product "Fedora" select Version : rawhide

  • Summary : Please branch and build <package> in epel9

At this point, things change depending on your ability or willingness to help.

Consumers / End Users

Clear out Description and put

Please branch and build <package> in epel9.

If there is no response after a week, add the following comment in the bug.

Will you be able to branch and build <package> in epel9.

If there is no action on the bug after another week, send an email to epel-devel asking if there are any packagers who would like to package and maintain your package on epel. Be sure to include the bugzilla URL in your email.

Fedora / EPEL Packagers

Clear out Description and put

Please branch and build <package> in epel9.

If you do not wish to maintain <package> in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package.

If there is no response after a week, add the following comment in the bug.

Will you be able to branch and build <package> in epel9.
I would be happy to be a co-maintainer if you do not wish
to build it on epel9.

If there is no action on the bug after another week, follow the Stalled EPEL Request steps, and open a ticket with releng

  • Ticket Title:

    • Stalled EPEL package: <package>

  • Ticket Body:

* Describe the issue
<package> is a stalled EPEL package.
Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time.
<bugzilla URL>
I am requesting <my_FAS_id> commit permissions so that I might branch and build this package in epel9.

<Fill out the other sections as you see fit>

After you have been given commit permissions, you can then branch, build, and maintain the package in epel.

EPEL Packaging SIG members

Clear out Description and put

Please branch and build <package> in epel9.

If you do not wish to maintain <package> in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packaging SIG would be happy to be a co-maintainer of the package.

If there is no response after a week, add the following comment in the bug.

Will you be able to branch and build <package> in epel9.
The EPEL Packaging SIG would be happy to be a co-maintainer
if you do not wish to build it on epel9.

If there is no action on the bug after another week, follow the Stalled EPEL Request steps, and open a ticket with releng

  • Ticket Title:

    • Stalled EPEL package: <package>

  • Ticket Body:

* Describe the issue
<package> is a stalled EPEL package.
Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time.
<bugzilla URL>
I am a member of the epel-packagers-sig and I am requesting epel-packagers-sig be given commit permissions so that I, or a member of the sig, might branch and build this package in epel9.

<Fill out the other sections as you see fit>

After the epel-packagers-sig has been given commit permissions, you can then branch, build, and maintain the package in epel.