Use common syntax for links
This commit is contained in:
parent
645e102dc0
commit
c95a77b63f
25 changed files with 131 additions and 131 deletions
|
|
@ -6,4 +6,4 @@ Most common use cases for examples is using output from an external script (for
|
|||
If you want to include this particular example somewhere, you can use the following syntax: `include::example$example-example.adoc[]`.
|
||||
Note the use of `example$` instead of an actual file location.
|
||||
|
||||
See link:https://docs.antora.org/antora/3.0/examples-directory/[Antora docs on examples] for more information about partials.
|
||||
See link:++https://docs.antora.org/antora/3.0/examples-directory/++[Antora docs on examples] for more information about partials.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ include::partial$attributes.adoc[]
|
|||
== Available packages in EPEL
|
||||
|
||||
Since EPEL is part of the Fedora project, you can search the available packages in the
|
||||
https://packages.fedoraproject.org/[Fedora Packages web app].
|
||||
link:++https://packages.fedoraproject.org/++[Fedora Packages web app].
|
||||
This provides an overview of available versions across various EPEL branches.
|
||||
If you find a package that is not yet available in the EPEL branch you would like it to be,
|
||||
please follow xref:epel-package-request.adoc[this guide] to request it.
|
||||
|
|
@ -13,23 +13,23 @@ please follow xref:epel-package-request.adoc[this guide] to request it.
|
|||
Alternately, you can browse the repo files directly:
|
||||
|
||||
* EPEL 10:
|
||||
https://dl.fedoraproject.org/pub/epel/10/Everything/x86_64/[x86_64],
|
||||
https://dl.fedoraproject.org/pub/epel/10/Everything/s390x/[s390x],
|
||||
https://dl.fedoraproject.org/pub/epel/10/Everything/ppc64le/[ppc64le],
|
||||
https://dl.fedoraproject.org/pub/epel/10/Everything/aarch64/[aarch64],
|
||||
https://dl.fedoraproject.org/pub/epel/10/Everything/source/tree/[sources]
|
||||
link:++https://dl.fedoraproject.org/pub/epel/10/Everything/x86_64/++[x86_64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/10/Everything/s390x/++[s390x],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/10/Everything/ppc64le/++[ppc64le],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/10/Everything/aarch64/++[aarch64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/10/Everything/source/tree/++[sources]
|
||||
* EPEL 9:
|
||||
https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/[x86_64],
|
||||
https://dl.fedoraproject.org/pub/epel/9/Everything/s390x/[s390x],
|
||||
https://dl.fedoraproject.org/pub/epel/9/Everything/ppc64le/[ppc64le],
|
||||
https://dl.fedoraproject.org/pub/epel/9/Everything/aarch64/[aarch64],
|
||||
https://dl.fedoraproject.org/pub/epel/9/Everything/source/tree/[sources]
|
||||
link:++https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/++[x86_64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/9/Everything/s390x/++[s390x],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/9/Everything/ppc64le/++[ppc64le],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/9/Everything/aarch64/++[aarch64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/9/Everything/source/tree/++[sources]
|
||||
* EPEL 8:
|
||||
https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/[x86_64],
|
||||
https://dl.fedoraproject.org/pub/epel/8/Everything/s390x/[s390x],
|
||||
https://dl.fedoraproject.org/pub/epel/8/Everything/ppc64le/[ppc64le],
|
||||
https://dl.fedoraproject.org/pub/epel/8/Everything/aarch64/[aarch64],
|
||||
https://dl.fedoraproject.org/pub/epel/8/Everything/SRPMS/[sources]
|
||||
link:++https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/++[x86_64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/8/Everything/s390x/++[s390x],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/8/Everything/ppc64le/++[ppc64le],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/8/Everything/aarch64/++[aarch64],
|
||||
link:++https://dl.fedoraproject.org/pub/epel/8/Everything/SRPMS/++[sources]
|
||||
|
||||
You can also browse these same directories on any of our
|
||||
https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL[mirrors].
|
||||
link:++https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL++[mirrors].
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ include::partial$attributes.adoc[]
|
|||
= EPEL branches
|
||||
|
||||
Fedora and EPEL package sources are maintained in
|
||||
https://src.fedoraproject.org[Fedora's dist-git].
|
||||
link:++https://src.fedoraproject.org++[Fedora's dist-git].
|
||||
The default branch is `rawhide`, corresponding to
|
||||
xref:releases::rawhide.adoc[Fedora Rawhide].
|
||||
Additional branches are used for other Fedora and EPEL releases.
|
||||
|
|
@ -23,7 +23,7 @@ for each minor version of RHEL 10.
|
|||
The `epel10` branch is used to create builds for the leading EPEL 10 minor version repository.
|
||||
Prior to the CentOS Stream 10 end of life
|
||||
(which corresponds to the end of the RHEL 10
|
||||
https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates[Full Support Phase]),
|
||||
link:++https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates++[Full Support Phase]),
|
||||
these builds are built against external repositories of the matching major version of CentOS Stream 10.
|
||||
|
||||
* CentOS Stream 10 BaseOS
|
||||
|
|
@ -38,7 +38,7 @@ They are published in the `pub/epel/10` dnf repository for consumption by CentOS
|
|||
|
||||
After the CentOS Stream 10 end of life
|
||||
(which corresponds to the beginning of the RHEL 10
|
||||
https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates[Maintenance Support Phase]),
|
||||
link:++https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates++[Maintenance Support Phase]),
|
||||
these builds are built against external repositories of the final minor version of RHEL 10.
|
||||
|
||||
* RHEL 10.10 BaseOS
|
||||
|
|
|
|||
|
|
@ -121,14 +121,14 @@ resolve the occasional compatibility issue. If you install both
|
|||
epel-release and epel-next-release, `dnf install ` should pick the
|
||||
correct available package from the appropriate repository. If that
|
||||
doesn't work, please file a
|
||||
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL[bug] to
|
||||
link:++https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL++[bug] to
|
||||
let the maintainer know.
|
||||
|
||||
[[how_do_i_report_a_package_that_needs_to_be_rebuilt_in_epel_next]]
|
||||
=== How do I report a package that needs to be rebuilt in EPEL Next?
|
||||
|
||||
File a
|
||||
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL[bug] to
|
||||
link:++https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL++[bug] to
|
||||
let the maintainer know.
|
||||
|
||||
[[why_does_epel_next_release_require_epel_release]]
|
||||
|
|
|
|||
|
|
@ -13,4 +13,4 @@ with updated, or changed packages in epel. EPEL Playground never really worked
|
|||
out and ended up being more burden than helpful.
|
||||
|
||||
If developers or maintainers want something similar to EPEL Playground we
|
||||
recommend https://copr.fedorainfracloud.org/[Fedora COPR], which has availability for EPEL builds.
|
||||
recommend link:++https://copr.fedorainfracloud.org/++[Fedora COPR], which has availability for EPEL builds.
|
||||
|
|
|
|||
|
|
@ -7,43 +7,43 @@ include::partial$attributes.adoc[]
|
|||
There are many ways to communicate with EPEL and its members:
|
||||
|
||||
// This syntax is needed to get asciidoc to accept the weird link characters.
|
||||
:epel-matrix: https://matrix.to/#/#epel:fedoraproject.org
|
||||
:epel-matrix: link:++https://matrix.to/#/#epel:fedoraproject.org++[]
|
||||
* The {epel-matrix}[epel:fedoraproject.org] channel on offers real-time
|
||||
support for EPEL users and developers.
|
||||
|
||||
* The https://web.libera.chat/?channels=#epel[#epel] IRC channel on
|
||||
https://libera.chat[Libera Chat] is a secondary chat location, but is not bridged to Matrix.
|
||||
* The link:++https://web.libera.chat/?channels=#epel++[#epel] IRC channel on
|
||||
link:++https://libera.chat++[Libera Chat] is a secondary chat location, but is not bridged to Matrix.
|
||||
|
||||
* The https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org/[epel-devel]
|
||||
* The link:++https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org/++[epel-devel]
|
||||
mailing list is for general EPEL discussion.
|
||||
https://www.redhat.com/archives/epel-devel-list/[Historic archives] are available.
|
||||
link:++https://www.redhat.com/archives/epel-devel-list/++[Historic archives] are available.
|
||||
|
||||
* The
|
||||
https://lists.fedoraproject.org/admin/lists/epel-announce@lists.fedoraproject.org/[epel-announce]
|
||||
link:++https://lists.fedoraproject.org/admin/lists/epel-announce@lists.fedoraproject.org/++[epel-announce]
|
||||
mailing list is a low volume mailing list for only important announcements.
|
||||
|
||||
* The
|
||||
https://lists.fedoraproject.org/admin/lists/epel-package-announce@lists.fedoraproject.org/[epel-package-announce]
|
||||
link:++https://lists.fedoraproject.org/admin/lists/epel-package-announce@lists.fedoraproject.org/++[epel-package-announce]
|
||||
mailing list is a list that gets information about package updates as they
|
||||
happen in the stable repository.
|
||||
|
||||
* If you find a bug in a EPEL maintained package, please report it to
|
||||
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora+EPEL[https://bugzilla.redhat.com/]
|
||||
link:++https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora+EPEL++[https://bugzilla.redhat.com/]
|
||||
under the "Fedora EPEL" product.
|
||||
|
||||
* Infrastructure issues (mirrors, repos, etc.) should be reported to
|
||||
https://pagure.io/releng/issues[Fedora releng].
|
||||
link:++https://pagure.io/releng/issues++[Fedora releng].
|
||||
|
||||
:meeting-matrix: https://matrix.to/#/#meeting-1:fedoraproject.org
|
||||
:meeting-matrix: link:++https://matrix.to/#/#meeting-1:fedoraproject.org++
|
||||
* The EPEL Steering Committee meets on Wednesday every week in the
|
||||
https://chat.fedoraproject.org/#/room/#meeting-1:fedoraproject.org[Fedora Meeting 1]
|
||||
link:++https://chat.fedoraproject.org/#/room/#meeting-1:fedoraproject.org++[Fedora Meeting 1]
|
||||
Matrix channel. The time is **not** tied to U.S. daylight savings time, so it is at
|
||||
18:00 UTC regardless of the time of year. Please check the time on the
|
||||
https://calendar.fedoraproject.org/epel/[epel calendar]; sometimes
|
||||
link:++https://calendar.fedoraproject.org/epel/++[epel calendar]; sometimes
|
||||
it can change or a meeting can be skipped. Feel free to join us! Logs of
|
||||
past meetings can be viewed in
|
||||
https://meetbot.fedoraproject.org/sresults/?group_id=epel&type=team[meetbot].
|
||||
link:++https://meetbot.fedoraproject.org/sresults/?group_id=epel&type=team++[meetbot].
|
||||
|
||||
* The EPEL Steering Committee has
|
||||
https://discussion.fedoraproject.org/t/join-us-for-the-epel-office-hours-every-month/37235[monthly
|
||||
link:++https://discussion.fedoraproject.org/t/join-us-for-the-epel-office-hours-every-month/37235++[monthly
|
||||
office hours for the EPEL project].
|
||||
|
|
|
|||
|
|
@ -9,10 +9,10 @@ include::partial$attributes.adoc[]
|
|||
=== What is EPEL?
|
||||
|
||||
Extra Packages for Enterprise Linux (EPEL) is an initiative within the
|
||||
https://fedoraproject.org/[Fedora Project]
|
||||
link:++https://fedoraproject.org/++[Fedora Project]
|
||||
to provide high quality additional packages for
|
||||
https://centos.org/[CentOS Stream] and
|
||||
https://redhat.com/rhel[Red Hat Enterprise Linux] (RHEL).
|
||||
link:++https://centos.org/++[CentOS Stream] and
|
||||
link:++https://redhat.com/rhel++[Red Hat Enterprise Linux] (RHEL).
|
||||
EPEL packages will also likely work with other distributions
|
||||
that target RHEL compatibility.
|
||||
|
||||
|
|
@ -226,12 +226,12 @@ xref:getting-started.adoc[getting started page].
|
|||
[[where_is_the_software_repository_located]]
|
||||
=== Where is the software repository located?
|
||||
|
||||
EPEL packages are located at the https://dl.fedoraproject.org/pub/epel/[main mirror]. There are mirrors
|
||||
available at
|
||||
https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL[mirror list].
|
||||
EPEL packages are located at the link:++https://dl.fedoraproject.org/pub/epel/++[main mirror].
|
||||
There are mirrors available at the
|
||||
link:++https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL++[mirror list].
|
||||
|
||||
The snapshots of the EPEL repository are available in an
|
||||
https://archives.fedoraproject.org/pub/archive/epel/[EPEL archive].
|
||||
link:++https://archives.fedoraproject.org/pub/archive/epel/++[EPEL archive].
|
||||
Those are useful when a package was removed from EPEL, e.g. because the
|
||||
package was added into a later RHEL version and you have not yet
|
||||
migrated to the latest RHEL version.
|
||||
|
|
@ -241,24 +241,24 @@ migrated to the latest RHEL version.
|
|||
|
||||
The main fedora download server is currently ipv4 only.
|
||||
|
||||
* https://dl.fedoraproject.org/pub/epel/[]
|
||||
* link:++https://dl.fedoraproject.org/pub/epel/++[]
|
||||
|
||||
It is recommended that you find the closest ipv6 mirror from the mirror list.
|
||||
|
||||
* https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL[]
|
||||
* link:++https://admin.fedoraproject.org/mirrormanager/mirrors/EPEL++[]
|
||||
|
||||
If you must connect directly to a fedora ipv6 download server, go here.
|
||||
|
||||
* https://download-ib01.fedoraproject.org/pub/epel/[]
|
||||
* link:++https://download-ib01.fedoraproject.org/pub/epel/++[]
|
||||
|
||||
[[where_can_i_find_help_or_report_issues]]
|
||||
=== Where can I find help or report issues?
|
||||
|
||||
You can find help or discuss issues on the
|
||||
https://admin.fedoraproject.org/mailman/listinfo/epel-devel[epel-devel]
|
||||
link:++https://admin.fedoraproject.org/mailman/listinfo/epel-devel++[epel-devel]
|
||||
mailing list or IRC channel #epel on libera.chat. Report issues against
|
||||
EPEL via
|
||||
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL[Bugzilla].
|
||||
link:++https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL++[Bugzilla].
|
||||
More options are available to
|
||||
xref:epel-communication.adoc[communicate with EPEL].
|
||||
|
||||
|
|
@ -266,7 +266,7 @@ xref:epel-communication.adoc[communicate with EPEL].
|
|||
=== How do I know that a package is a EPEL package?
|
||||
|
||||
All EPEL packages are signed with an official EPEL gpg-key. The public
|
||||
key IDs can be found at https://getfedora.org/security/. The keys are
|
||||
key IDs can be found at link:++https://getfedora.org/security/++[]. The keys are
|
||||
included in epel-release and dnf will ask you to import it the first
|
||||
time you install an EPEL package.
|
||||
|
||||
|
|
@ -402,11 +402,11 @@ The easiest ways to do this are to either use the
|
|||
xref:epel-rhel-entitlements.adoc[RHEL developer subscription]
|
||||
or check the RHEL package manifests.
|
||||
|
||||
* https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html-single/package_manifest/index[RHEL 9 package manifest]
|
||||
* https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html-single/package_manifest/index[RHEL 8 package manifest]
|
||||
* link:++https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html-single/package_manifest/index++[RHEL 9 package manifest]
|
||||
* link:++https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/8/html-single/package_manifest/index++[RHEL 8 package manifest]
|
||||
|
||||
You can also check the package source repos in the
|
||||
https://gitlab.com/redhat/centos-stream/rpms[CentOS Stream GitLab space].
|
||||
link:++https://gitlab.com/redhat/centos-stream/rpms++[CentOS Stream GitLab space].
|
||||
Note that a GitLab branch corresponds to the same major version of RHEL,
|
||||
e.g. the c9s branch for RHEL 9.
|
||||
If a branch has a `dead.package` file,
|
||||
|
|
@ -441,11 +441,11 @@ co-maintainer
|
|||
* Long Term: Request the package be added to RHEL 8 and 9 CRB
|
||||
repository.
|
||||
** To initiate this process, please file an issue in
|
||||
https://issues.redhat.com and request it be added to RHEL 8 and 9.
|
||||
link:++https://issues.redhat.com++[] and request it be added to RHEL 8 and 9.
|
||||
Report the bug against the RHEL project, assign it to the proper
|
||||
CentOS Stream versions and add the source package name in the Component field.
|
||||
More details on this can be found in the
|
||||
https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue[CentOS contributor guide].
|
||||
link:++https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue++[CentOS contributor guide].
|
||||
** Be sure to say that it is impacting an EPEL build, and which package
|
||||
it is impacting.
|
||||
|
||||
|
|
@ -454,14 +454,14 @@ it is impacting.
|
|||
|
||||
When EPEL 8 was launched, it came together with the EPEL 8
|
||||
Modular repo as an effort to bring modular packages to EPEL. After years of struggle,
|
||||
https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/LNNPYQU6OLT2OMGKJM6DXLCE5RIJ57HJ/[it was decided]
|
||||
link:++https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/LNNPYQU6OLT2OMGKJM6DXLCE5RIJ57HJ/++[it was decided]
|
||||
to disable by default the EPEL 8 Modular repository on October 31st 2022, and then
|
||||
to archive the repository from Febraury 14th 2023 onward.
|
||||
Currently there is no plan to bring modularity back to EPEL.
|
||||
|
||||
If you want to bring a package that is distributed as modular in Fedora
|
||||
you will need to create a
|
||||
https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple[non-modular version of the package].
|
||||
link:++https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple++[non-modular version of the package].
|
||||
|
||||
== Miscellaneous
|
||||
|
||||
|
|
@ -541,7 +541,7 @@ Some people nevertheless do it and the dnf priorities plugin can help to avoid t
|
|||
|
||||
If you encounter a problem where packages from EPEL are incompatible with another repository,
|
||||
or lead dnf to bail out during dependency resolution,
|
||||
please report a bug in https://bugzilla.redhat.com[Bugzilla]
|
||||
please report a bug in link:++https://bugzilla.redhat.com++[Bugzilla]
|
||||
and contact the maintainer of the other repositories.
|
||||
The EPEL project encourages its maintainers to solve such problems together
|
||||
with the maintainers from other repositories
|
||||
|
|
|
|||
|
|
@ -15,4 +15,4 @@ EPEL strives to ship packages that are as stable and bug free as possible. Testi
|
|||
|
||||
== Release Engineering ==
|
||||
|
||||
EPEL Release engineering is responsible for making sure packages are built and signed and mirrored out. Currently this group is a subset of the Fedora Release Engineering group. See the link:https://docs.pagure.org/releng/contributing.html[Fedora Release Engineering page] for more information.
|
||||
EPEL Release engineering is responsible for making sure packages are built and signed and mirrored out. Currently this group is a subset of the Fedora Release Engineering group. See the link:++https://docs.pagure.org/releng/contributing.html++[Fedora Release Engineering page] for more information.
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ lives on in case you do not.
|
|||
|
||||
This role includes maintaining one or more packages through the Fedora
|
||||
Project. These packages are rebuilt in the Fedora Extra Packages for
|
||||
Enterprise Linux (EPEL) repository (https://fedoraproject.org/wiki/EPEL).
|
||||
Enterprise Linux (EPEL) repository (link:++https://fedoraproject.org/wiki/EPEL++[]).
|
||||
The list of packages is not specified here, because it may need to
|
||||
fluctuate over time, but a list should be maintained with the group
|
||||
manager/project lead.
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ for information about getting a free RHEL subscription for EPEL package maintena
|
|||
|
||||
The best way to get a new package into EPEL is to first get it added to
|
||||
Fedora. You can add such packages to the
|
||||
https://fedoraproject.org/wiki/Package_maintainers_wishlist[wish list for Fedora].
|
||||
link:++https://fedoraproject.org/wiki/Package_maintainers_wishlist++[wish list for Fedora].
|
||||
|
||||
It is possible to have packages only in EPEL, for example if the
|
||||
functionality has already been merged in a more recent package in
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ The *source package* name is used as the bugzilla component field.
|
|||
This may or may not be the same as the package name you are looking for.
|
||||
If you are not sure what the source package name is,
|
||||
search for your desired package in the
|
||||
https://packages.fedoraproject.org/[Fedora Packages web app].
|
||||
link:++https://packages.fedoraproject.org/++[Fedora Packages web app].
|
||||
Once you locate the desired package in this app,
|
||||
the URL will have the following structure:
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ 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 two more weeks, send an email to https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org/[epel-devel] asking if there are any packagers
|
||||
If there is no action on the bug after two more weeks, send an email to link:++https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org/++[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_packagers]]
|
||||
|
|
@ -120,7 +120,7 @@ I would be happy to be a co-maintainer if you do not wish
|
|||
to build it on epel9 (FAS: <your FAS Id>).
|
||||
....
|
||||
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with https://pagure.io/releng/issues/[releng]
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
|
||||
* Ticket Title:
|
||||
** Stalled EPEL package: <package>
|
||||
|
|
@ -167,7 +167,7 @@ The EPEL Packagers 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 two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with https://pagure.io/releng/issues/[releng]
|
||||
If there is no action on the bug after two more weeks, follow the xref:epel-package-request.adoc#stalled_epel_requests[Stalled EPEL Request steps], and open a ticket with link:++https://pagure.io/releng/issues/++[releng]
|
||||
|
||||
* Ticket Title:
|
||||
** Stalled EPEL package: <package>
|
||||
|
|
@ -200,7 +200,7 @@ are willing to help maintain / co-maintain that package in EPEL-X.
|
|||
package in EPEL and set a needinfo flag for the maintainer.
|
||||
** This is in case the initial message was missed.
|
||||
* Two weeks go by with no response.
|
||||
* They file a https://pagure.io/releng/issues/[rel-eng ticket], that
|
||||
* They file a link:++https://pagure.io/releng/issues/++[rel-eng ticket], that
|
||||
points to the Bugzilla bug, requesting appropriate privileges to be able to
|
||||
branch and build that package in EPEL-X
|
||||
** This part of the policy will adjust as various features get
|
||||
|
|
|
|||
|
|
@ -8,13 +8,13 @@ include::partial$attributes.adoc[]
|
|||
|
||||
EPEL Packagers SIG is a dist-git group. Being a member of that
|
||||
group allows you to work with packages that have added the
|
||||
https://src.fedoraproject.org/group/epel-packagers-sig[epel-packagers-sig group]
|
||||
link:++https://src.fedoraproject.org/group/epel-packagers-sig++[epel-packagers-sig group]
|
||||
as a collaborator on their packages. You will be able to
|
||||
branch, build and work on those EPEL packages.
|
||||
|
||||
You do not need to be a member of the EPEL Packagers SIG to build packages on EPEL.
|
||||
|
||||
https://accounts.fedoraproject.org/group/epel-packagers-sig/[EPEL Packagers SIG Sponsors] are SIG members that are also
|
||||
link:++https://accounts.fedoraproject.org/group/epel-packagers-sig/++[EPEL Packagers SIG Sponsors] are SIG members that are also
|
||||
on the EPEL Steering Committee.
|
||||
|
||||
== Why
|
||||
|
|
@ -35,7 +35,7 @@ of EPEL faster.
|
|||
== Workflow
|
||||
|
||||
We aim to be somewhere in between the language-based SIGs (e.g. the
|
||||
https://fedoraproject.org/wiki/SIGs/Python[Python SIG]) and being "provenpackagers for EPEL":
|
||||
link:++https://fedoraproject.org/wiki/SIGs/Python++[Python SIG]) and being "provenpackagers for EPEL":
|
||||
|
||||
* like the language-based SIG, it's opt in: if a package maintainer
|
||||
would like help maintaining their packages for EPEL, they can add
|
||||
|
|
@ -55,13 +55,13 @@ Automatic branching is not implemented yet.
|
|||
=== Packages
|
||||
|
||||
Candidate packages for onboarding --
|
||||
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14[NEW
|
||||
link:++https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14++[NEW
|
||||
branch requests over two weeks old]. We should consider reviewing this
|
||||
periodically.
|
||||
|
||||
Branch requests and/or bug requests that need to be brought into the
|
||||
SIG's attention should block
|
||||
https://bugzilla.redhat.com/show_bug.cgi?id=EPELPackagersSIG[the
|
||||
link:++https://bugzilla.redhat.com/show_bug.cgi?id=EPELPackagersSIG++[the
|
||||
EPELPackagersSIG tracker].
|
||||
|
||||
See xref:epel-package-request.adoc#stalled_epel_requests[the guidelines
|
||||
|
|
@ -83,9 +83,9 @@ have been packaging with Fedora and/or EPEL for at least a year.
|
|||
The procedure is similar to that
|
||||
for xref:fesco::Provenpackager_policy.adoc#_becoming_provenpackager[provenpackagers].
|
||||
|
||||
* File a ticket in the https://pagure.io/epel/issues[EPEL issue tracker] indicating why you wish to
|
||||
* File a ticket in the link:++https://pagure.io/epel/issues++[EPEL issue tracker] indicating why you wish to
|
||||
become a member.
|
||||
* A https://accounts.fedoraproject.org/group/epel-packagers-sig/[Packagers SIG Sponsor] will send an e-mail to the SIG members, so they
|
||||
* A link:++https://accounts.fedoraproject.org/group/epel-packagers-sig/++[Packagers SIG Sponsor] will send an e-mail to the SIG members, so they
|
||||
are aware about the ticket.
|
||||
* Packagers SIG Sponsors vote in the EPEL ticket.
|
||||
* You must get at least 1 positive votes from SIG Sponsor with no negative
|
||||
|
|
@ -96,13 +96,13 @@ If you haven’t been approved after one week, the EPEL Steering Committee will
|
|||
|
||||
=== Get to work
|
||||
|
||||
* Look through https://pagure.io/epel/issues[the general EPEL issues] related to packaging and see where you can help.
|
||||
* Look through https://bugzilla.redhat.com/show_bug.cgi?id=EPELPackagersSIG[the EPEL Packagers SIG bug tracker], see if there are any you want to help with.
|
||||
* Look through https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14[old epel bugs]. Many of them are requesting packages. See if there are any you think should be added to the EPEL Packagers Sig tracker.
|
||||
* Look at https://packager-dashboard.fedoraproject.org/dashboard?groups=epel-packagers-sig[the EPEL Packagers SIG dashboard] to see if there is anything there you can do.
|
||||
* Look at https://tdawson.fedorapeople.org/epel/willit/status-overall.html[Will-It-Install] and see if there are any packages that will not install that you can help with.
|
||||
** https://tdawson.fedorapeople.org/epel/willit/epel9/status-wont-install.html[EPEL 9 packages that will not install].
|
||||
** https://tdawson.fedorapeople.org/epel/willit/epel8/status-wont-install.html[EPEL 8 packages that will not install].
|
||||
* Look through link:++https://pagure.io/epel/issues++[the general EPEL issues] related to packaging and see where you can help.
|
||||
* Look through link:++https://bugzilla.redhat.com/show_bug.cgi?id=EPELPackagersSIG++[the EPEL Packagers SIG bug tracker], see if there are any you want to help with.
|
||||
* Look through link:++https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14++[old epel bugs]. Many of them are requesting packages. See if there are any you think should be added to the EPEL Packagers Sig tracker.
|
||||
* Look at link:++https://packager-dashboard.fedoraproject.org/dashboard?groups=epel-packagers-sig++[the EPEL Packagers SIG dashboard] to see if there is anything there you can do.
|
||||
* Look at link:++https://tdawson.fedorapeople.org/epel/willit/status-overall.html++[Will-It-Install] and see if there are any packages that will not install that you can help with.
|
||||
** link:++https://tdawson.fedorapeople.org/epel/willit/epel9/status-wont-install.html++[EPEL 9 packages that will not install].
|
||||
** link:++https://tdawson.fedorapeople.org/epel/willit/epel8/status-wont-install.html++[EPEL 8 packages that will not install].
|
||||
|
||||
See xref:epel-package-request.adoc#stalled_epel_requests[the guidelines
|
||||
for stalled requests] for follow-ups if a branch request has been stale
|
||||
|
|
|
|||
|
|
@ -33,19 +33,19 @@ This does not mean that EPEL packages should incorrectly identify
|
|||
a dependency as weak (e.g. changing a Requires to a Recommends).
|
||||
On a case by case basis, exceptions to this policy may be granted
|
||||
by the EPEL Steering Committee.
|
||||
To request an exception https://pagure.io/epel/issues[open an issue]
|
||||
To request an exception link:++https://pagure.io/epel/issues++[open an issue]
|
||||
and add the "meeting" tag.
|
||||
|
||||
[[eln]]
|
||||
== ELN
|
||||
|
||||
https://docs.fedoraproject.org/en-US/eln/[ELN] is a new buildroot and compose
|
||||
link:++https://docs.fedoraproject.org/en-US/eln/++[ELN] is a new buildroot and compose
|
||||
process for Fedora that takes Fedora Rawhide dist-git sources and emulate a Red
|
||||
Hat Enterprise Linux compose. The packages included are thus based on what is
|
||||
planned to be included in the next major RHEL release, and in that way it is
|
||||
already useful for EPEL packagers.
|
||||
|
||||
https://docs.fedoraproject.org/en-US/eln/extras/[ELN Extras], however, is an
|
||||
link:++https://docs.fedoraproject.org/en-US/eln/extras/++[ELN Extras], however, is an
|
||||
extension that is mostly driven by EPEL packagers. Given that one of the pain
|
||||
points in bootstrapping a new EPEL is in processing the dependency graph of the
|
||||
packages our packagers are _actually_ interested in (whether they are a library
|
||||
|
|
@ -53,7 +53,7 @@ that some in-house or ISV software needs, or a tool) and getting them branched
|
|||
and built, we can use ELN Extras in this way:
|
||||
|
||||
* add packages to ELN Extras' content resolver input, e.g.
|
||||
https://github.com/minimization/content-resolver-input/blob/master/configs/eln_extras_kde.yaml[KDE
|
||||
link:++https://github.com/minimization/content-resolver-input/blob/master/configs/eln_extras_kde.yaml++[KDE
|
||||
packages]; note that this has sufficient metadata to indicate who will
|
||||
maintain such packages
|
||||
* check the
|
||||
|
|
@ -78,7 +78,7 @@ backports are not feasible and/or wanted, we will list them here.
|
|||
== RPM macros
|
||||
|
||||
Not all macros defined in (or built into) existing Fedora packages
|
||||
will work when a spec is converted for use in EPEL. https://src.fedoraproject.org/rpms/epel-rpm-macros/[epel-rpm-macros]
|
||||
will work when a spec is converted for use in EPEL. link:++https://src.fedoraproject.org/rpms/epel-rpm-macros/++[epel-rpm-macros]
|
||||
backports the newer macros and is installed by default in EPEL
|
||||
mock chroots.
|
||||
|
||||
|
|
@ -104,7 +104,7 @@ Python 2 packages should also refer to the Python 2 section of the
|
|||
xref:packaging-guidelines::Python_Appendix.adoc#_python_2_packages[Fedora Python Packaging Appendix].
|
||||
New Python 2 packages *SHOULD NOT* be added to EPEL 8,
|
||||
because the RHEL 8 Python 2.7 Application Stream will be
|
||||
https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle[retired in June 2024].
|
||||
link:++https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle++[retired in June 2024].
|
||||
|
||||
=== Automatically generated dependencies
|
||||
|
||||
|
|
@ -115,9 +115,9 @@ is enabled by default for EPEL 8 and EPEL 9 builds.
|
|||
The dependency generator in RHEL 8 is significantly limited compared to the one in Fedora and RHEL 9.
|
||||
Simple dependencies and minimum/maximum versions work correctly,
|
||||
but more advanced specifications such as
|
||||
https://peps.python.org/pep-0508/#environment-markers[environment markers]
|
||||
link:++https://peps.python.org/pep-0508/#environment-markers++[environment markers]
|
||||
and
|
||||
https://peps.python.org/pep-0440/#compatible-release[compatible release clauses]
|
||||
link:++https://peps.python.org/pep-0440/#compatible-release++[compatible release clauses]
|
||||
do not.
|
||||
This can lead to missing dependencies,
|
||||
included dependencies that should have been skipped,
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ maintainer is unable to backport just the security fix.
|
|||
== Process for incompatible upgrades
|
||||
|
||||
. Send e-mail to
|
||||
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/[epel-devel]
|
||||
link:++lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/++[epel-devel]
|
||||
with details of the proposed upgrade. Include items such as the CVE of
|
||||
the security issue to be fixed, and/or an upstream bug tracker reference
|
||||
(if applicable). Also reference a bug in
|
||||
|
|
@ -27,7 +27,7 @@ xref:epel-communication.adoc[Bugzilla] against the
|
|||
package.
|
||||
. In the case of a critical CVE the maintainer *MAY* build the package
|
||||
and submit it to bodhi for testing. 'Auto-request stable?' *MUST NOT* be checked.
|
||||
. File an https://pagure.io/epel/issues[EPEL issue]. This can be done while
|
||||
. File an link:++https://pagure.io/epel/issues++[EPEL issue]. This can be done while
|
||||
discussion is ongoing; please link to the thread in the mailing list archive so the EPEL
|
||||
Steering Committee can monitor the discussion and know when it is ready to be discussed.
|
||||
. After a week of mailing list discussion, an EPEL Steering Committee member will add the
|
||||
|
|
|
|||
|
|
@ -49,12 +49,12 @@ xref:epel-packaging-examples.adoc#_missing_but_built_examples[Short Term Example
|
|||
Request the package be added to the appropriate RHEL CRB repository.
|
||||
|
||||
* To initiate this process,
|
||||
please file an issue in https://issues.redhat.com and request it be added to RHEL.
|
||||
please file an issue in link:++https://issues.redhat.com++ and request it be added to RHEL.
|
||||
Report the bug against the RHEL project,
|
||||
assign it to the proper CentOS Stream versions,
|
||||
and add the source package name in the Component field.
|
||||
More details on this can be found in the
|
||||
https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue[CentOS contributor guide].
|
||||
link:++https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue++[CentOS contributor guide].
|
||||
* Be sure to say that it is impacting an EPEL build, and which package it is impacting.
|
||||
|
||||
....
|
||||
|
|
|
|||
|
|
@ -21,8 +21,8 @@ is going to be in RHEL. It should also say which RHEL release it will be in (e.
|
|||
|
||||
*Do not remove your EPEL package until you have verified that it is in RHEL.*
|
||||
|
||||
* If the package version in RHEL is older than the version in EPEL, send an e-mail to https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/[epel-devel], documenting the potential loss of functionality. If the package version in RHEL is the same or newer, sending the e-mail is optional
|
||||
* Once your package is in RHEL, you should https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure[retire the package from EPEL].
|
||||
* If the package version in RHEL is older than the version in EPEL, send an e-mail to link:++https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/++[epel-devel], documenting the potential loss of functionality. If the package version in RHEL is the same or newer, sending the e-mail is optional
|
||||
* Once your package is in RHEL, you should link:++https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure++[retire the package from EPEL].
|
||||
** fedpkg switch-branch epel8 (or whichever epel branch is correct)
|
||||
** fedpkg retire "REASON FOR RETIREMENT"
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ an incompatible upgrade]. If the EPEL version is fairly old, and a newer versio
|
|||
cannot be built, it's possible that the only choice of action is to remove the package.
|
||||
|
||||
. Send e-mail to
|
||||
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/[epel-devel]
|
||||
link:++https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/++[epel-devel]
|
||||
with details of the proposed retirement. Include items such as the CVE of
|
||||
the security issues affecting the existing version, and/or an upstream
|
||||
bug tracker reference (if applicable). Also reference a bug in
|
||||
|
|
@ -46,7 +46,7 @@ is for a critical security update such as remote root.
|
|||
announce the retirement and specific actions that users must
|
||||
take in order to continue using the software
|
||||
(e.g. install using `pip` or some other delivery mechanism).
|
||||
. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure[Retire the package from EPEL].
|
||||
. link:++https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure++[Retire the package from EPEL].
|
||||
** fedpkg switch-branch epel8 (or whichever epel branch is correct)
|
||||
** fedpkg retire "REASON FOR RETIREMENT"
|
||||
|
||||
|
|
@ -57,16 +57,16 @@ EPEL is run and maintained by many volunteers. A person's life, job,
|
|||
and priorities change over time. It is natural that a time might come that you no
|
||||
longer have the time or desire to maintain a package.
|
||||
|
||||
. Check if there are other maintainers of the package. https://src.fedoraproject.org/rpms/nedit[https://src.fedoraproject.org/rpms/<package>]
|
||||
. Check if there are other maintainers of the package. link:++https://src.fedoraproject.org/rpms/nedit++[https://src.fedoraproject.org/rpms/<package>]
|
||||
If there are, ask them if they would like to maintain the epel branches.
|
||||
. If none of the other maintainers want to maintain the epel branches, send an e-mail to
|
||||
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/[epel-devel]. Let us
|
||||
link:++https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/++[epel-devel]. Let us
|
||||
know you cannot maintain the package anymore, and none of the other maintainers can either. If there
|
||||
is anything special about the package, or urgent issues such as the package not being installable, let us know that as well.
|
||||
. After two weeks, If nobody has volunteered to take over the package for you, send an e-mail to epel-announce. It should
|
||||
announce the retirement and specific actions that users must take in order to continue using the software
|
||||
(e.g. install using `pip` or some other delivery mechanism).
|
||||
. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure[Retire the package from EPEL].
|
||||
. link:++https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure++[Retire the package from EPEL].
|
||||
** fedpkg switch-branch epel8 (or whichever epel branch is correct)
|
||||
** fedpkg retire "REASON FOR RETIREMENT"
|
||||
|
||||
|
|
@ -80,7 +80,7 @@ Packages that once were installable, but no longer are. Packages that were neve
|
|||
=== Process: Once installable
|
||||
|
||||
If a package was once installable, but no longer is, try to fix the problem. If you cannot, or you do not have the
|
||||
time or desire to fix it, follow the https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_no_time_or_desire[No Time or Desire policy]
|
||||
time or desire to fix it, follow the link:++https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_no_time_or_desire++[No Time or Desire policy]
|
||||
|
||||
[[process_never_installable]]
|
||||
=== Process: Never installable
|
||||
|
|
@ -88,6 +88,6 @@ time or desire to fix it, follow the https://docs.fedoraproject.org/en-US/epel/e
|
|||
If a package was never installable in an EPEL repo, try to fix the problem. If you cannot fix the problem and wish
|
||||
to retire the package from that EPEL branch / repo, you can.
|
||||
|
||||
. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure[Retire the package from EPEL].
|
||||
. link:++https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#_procedure++[Retire the package from EPEL].
|
||||
** fedpkg switch-branch epel8 (or whichever epel branch is correct)
|
||||
** fedpkg retire "REASON FOR RETIREMENT"
|
||||
|
|
|
|||
|
|
@ -18,4 +18,4 @@ EPEL will not provide any SCLs.
|
|||
|
||||
For use cases that require the parallel installation of multiple
|
||||
versions of the same component, EPEL recommends the same solution as
|
||||
Fedora in the https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple[Fedora Packaging Guidelines].
|
||||
Fedora in the link:++https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple++[Fedora Packaging Guidelines].
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ In 2023 the committee decided that members would be elected. The first election
|
|||
|
||||
From EPEL's beginning (2007) until 2024, committee members were based on the most active members when new seats needed to be filled.
|
||||
Starting in 2024, Steering Committee members will be elected for two year terms.
|
||||
EPEL Streeing Committee elections will be part of the https://docs.fedoraproject.org/en-US/program_management/elections/[Fedora elections process].
|
||||
EPEL Streeing Committee elections will be part of the link:++docs.fedoraproject.org/en-US/program_management/elections/++[Fedora elections process].
|
||||
EPEL committee elections will occur during the first Fedora election cycle of a calendar year.
|
||||
|
||||
[[committee_members]]
|
||||
|
|
@ -78,14 +78,14 @@ The meeting is public and everyone is invited.
|
|||
=== Committee meeting voting
|
||||
|
||||
The EPEL Steering Committee tracks ongoing decisions using the
|
||||
https://pagure.io/epel/issues[EPEL ticketing system].
|
||||
link:++https://pagure.io/epel/issues++[EPEL ticketing system].
|
||||
Decisions are voted on at the weekly Steering Committee meeting.
|
||||
These decisions usually fall into one of these categories:
|
||||
|
||||
* tickets asking for a change in EPEL policy
|
||||
* tickets asking for an exception to EPEL policy
|
||||
* tickets requesting approval for an
|
||||
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/[incompatible upgrade]
|
||||
link:++https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/++[incompatible upgrade]
|
||||
|
||||
Eligible voters are all currently-serving members of the Steering Committee.
|
||||
If a member is unable to attend a meeting,
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ xref:packaging-guidelines::index.adoc[packaging guidelines], the
|
|||
xref:packaging-guidelines::index.adoc#_naming[package naming guidelines], and the
|
||||
xref:packaging-guidelines::ReviewGuidelines.adoc[package review guidelines] that are designed
|
||||
and maintained by the xref:fesco::index.adoc[FESCo], and
|
||||
https://fedoraproject.org/wiki/Packaging_Committee[Packaging Committee]. EPEL-specific exceptions
|
||||
link:++https://fedoraproject.org/wiki/Packaging_Committee++[Packaging Committee]. EPEL-specific exceptions
|
||||
are documented here and in the xref:epel-packaging.adoc[EPEL Packaging] page.
|
||||
|
||||
Please note that the sections "Guidelines" and "Policies" use their
|
||||
|
|
@ -303,7 +303,7 @@ still in Fedora.
|
|||
== Policy for end-of-life releases
|
||||
|
||||
When a RHEL release reaches the end of the
|
||||
https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates[Maintenance Support phase,title=RHEL life cycle],
|
||||
link:++https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates++[Maintenance Support phase,title=RHEL life cycle],
|
||||
the corresponding EPEL release also goes end-of-life.
|
||||
On the day maintenance support ends for the RHEL release,
|
||||
Koji build targets are removed,
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Packages entering the EPEL collection MUST spend 2 weeks or until they
|
|||
reach +3 karma in the updates system before being promoted as a stable
|
||||
update. During this time they are in the xref:epel-testing.adoc[epel-testing]
|
||||
repository. Everyone is encouraged to install and test packages from this
|
||||
repository and provide feedback. The https://admin.fedoraproject.org/updates[Bodhi
|
||||
repository and provide feedback. The link:++https://admin.fedoraproject.org/updates++[Bodhi
|
||||
web interface] is one place to provide feedback. You can also use the
|
||||
'fedora-easy-karma' package to quickly provide feedback on all the
|
||||
packages you have installed from the epel-testing repository.
|
||||
|
|
|
|||
|
|
@ -4,11 +4,11 @@ include::partial$attributes.adoc[]
|
|||
= RHEL entitlements for EPEL maintainers
|
||||
|
||||
EPEL maintainers can use the free
|
||||
https://developers.redhat.com[RHEL developer subscription]
|
||||
link:++https://developers.redhat.com++[RHEL developer subscription]
|
||||
to develop and test their packages.
|
||||
The https://rpm-software-management.github.io/mock/[mock] tool includes
|
||||
The link:++https://rpm-software-management.github.io/mock/++[mock] tool includes
|
||||
`rhel+epel-<version>-<arch>.cfg` configuration files that
|
||||
https://rpm-software-management.github.io/mock/Feature-rhelchroots[integrate with this subscription],
|
||||
link:++https://rpm-software-management.github.io/mock/Feature-rhelchroots++[integrate with this subscription],
|
||||
even on non-RHEL distributions such as Fedora.
|
||||
|
||||
An EPEL maintainer may alternatively use other RHEL-like distributions to develop and test their packages.
|
||||
|
|
|
|||
|
|
@ -5,9 +5,9 @@ include::partial$attributes.adoc[]
|
|||
|
||||
The *epel-testing* repository contains updates scheduled to be released
|
||||
for the maintained releases of EPEL. User testing and feedback provided
|
||||
via https://bodhi.fedoraproject.org[Bodhi], on the
|
||||
https://admin.fedoraproject.org/mailman/listinfo/epel-devel[epel-devel]
|
||||
mailing list and the relevant https://bugzilla.redhat.com[Bugzilla] is
|
||||
via link:++https://bodhi.fedoraproject.org++[Bodhi], on the
|
||||
link:++https://admin.fedoraproject.org/mailman/listinfo/epel-devel++[epel-devel]
|
||||
mailing list and the relevant link:++https://bugzilla.redhat.com++[Bugzilla] is
|
||||
vital to ensure that good updates are released quickly and bad ones kept
|
||||
away from release.
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ dnf --enablerepo epel-testing install <foo>
|
|||
[[what_to_test_testing_and_reporting_results]]
|
||||
== What to test, testing, and reporting results
|
||||
|
||||
The https://bodhi.fedoraproject.org[Bodhi] system is used to track and
|
||||
The link:++https://bodhi.fedoraproject.org++[Bodhi] system is used to track and
|
||||
collate feedback on testing updates. All testing updates will be shown
|
||||
in the Bodhi system. First of all, if any test update package works
|
||||
worse for you in any respect than the pre-update version did, this is a
|
||||
|
|
@ -78,10 +78,10 @@ possible, test that the update does indeed fix the issues it claims to
|
|||
fix.
|
||||
|
||||
You can give your feedback on a test update by using the
|
||||
https://bodhi.fedoraproject.org[Bodhi web interface]. There is a _Login_
|
||||
link:++https://bodhi.fedoraproject.org++[Bodhi web interface]. There is a _Login_
|
||||
link in the left-hand sidebar. Log in using your Fedora account. If you
|
||||
don't have a Fedora account, you can
|
||||
https://admin.fedoraproject.org/accounts/user/new[create an account
|
||||
link:++https://admin.fedoraproject.org/accounts/user/new++[create an account
|
||||
here]. Once you are logged in, you will be able to leave a comment on
|
||||
the update. Underneath the comment box are three options: _Untested_,
|
||||
_Works for me_, and _Does not work_. For a guide on when to leave each
|
||||
|
|
@ -99,4 +99,4 @@ released quickly and bad ones don't get out to the general public.
|
|||
[[see_also]]
|
||||
== See also
|
||||
|
||||
* https://fedoraproject.org/wiki/Bodhi[Bodhi Guide]
|
||||
* link:++https://fedoraproject.org/wiki/Bodhi++[Bodhi Guide]
|
||||
|
|
|
|||
|
|
@ -20,10 +20,10 @@ The EPEL project recommends using the official permalinks on this page to ensure
|
|||
|
||||
== Release package permalinks
|
||||
|
||||
* https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm[epel-release-latest-10]
|
||||
* https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-9.noarch.rpm[epel-next-release-latest-9]
|
||||
* https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm[epel-release-latest-9]
|
||||
* https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm[epel-release-latest-8]
|
||||
* link:++https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm++[epel-release-latest-10]
|
||||
* link:++https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-9.noarch.rpm++[epel-next-release-latest-9]
|
||||
* link:++https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm++[epel-release-latest-9]
|
||||
* link:++https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm++[epel-release-latest-8]
|
||||
|
||||
== EL10
|
||||
|
||||
|
|
@ -146,7 +146,7 @@ method for working with these is to have a newer system mirror the
|
|||
entire archive and then for your systems to point to that mirror.
|
||||
====
|
||||
|
||||
* EPEL 7: https://dl.fedoraproject.org/pub/archive/epel/7/
|
||||
* EPEL 6: https://dl.fedoraproject.org/pub/archive/epel/6/
|
||||
* EPEL 5: https://dl.fedoraproject.org/pub/archive/epel/5/
|
||||
* EPEL 4: https://dl.fedoraproject.org/pub/archive/epel/4/
|
||||
* EPEL 7: link:++https://dl.fedoraproject.org/pub/archive/epel/7/++[]
|
||||
* EPEL 6: link:++https://dl.fedoraproject.org/pub/archive/epel/6/++[]
|
||||
* EPEL 5: link:++https://dl.fedoraproject.org/pub/archive/epel/5/++[]
|
||||
* EPEL 4: link:++https://dl.fedoraproject.org/pub/archive/epel/4/++[]
|
||||
|
|
|
|||
|
|
@ -21,10 +21,10 @@ are available for each version.
|
|||
== What is Extra Packages for Enterprise Linux (or EPEL)?
|
||||
|
||||
Extra Packages for Enterprise Linux (EPEL) is an initiative within the
|
||||
https://fedoraproject.org/[Fedora Project]
|
||||
link:++https://fedoraproject.org/++[Fedora Project]
|
||||
to provide high quality additional packages for
|
||||
https://centos.org/[CentOS Stream] and
|
||||
https://redhat.com/rhel[Red Hat Enterprise Linux] (RHEL).
|
||||
link:++https://centos.org/++[CentOS Stream] and
|
||||
link:++https://redhat.com/rhel++[Red Hat Enterprise Linux] (RHEL).
|
||||
|
||||
EPEL packages are usually based on their Fedora counterparts
|
||||
and should not conflict with or replace packages in the base Enterprise Linux distributions.
|
||||
|
|
|
|||
|
|
@ -12,4 +12,4 @@ In these cases, you can use a partial to include the same content in multiple pl
|
|||
If you want to include this particular example somewhere, you can use the following syntax: `include::partial$partial-example.adoc[]`.
|
||||
Note the use of `partial$` instead of an actual file location.
|
||||
|
||||
See link:https://docs.antora.org/antora/3.0/partials-directory/[Antora docs on partials] for more information about partials.
|
||||
See link:++https://docs.antora.org/antora/3.0/partials-directory/++[Antora docs on partials] for more information about partials.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue