From 7ddbaf2572fb614c12fdb6a6799ba2c91d0bd92a Mon Sep 17 00:00:00 2001 From: Carl George Date: Jul 24 2024 14:45:13 +0000 Subject: Replace mentions of CentOS (classic) with CentOS Stream --- diff --git a/modules/ROOT/pages/epel-about.adoc b/modules/ROOT/pages/epel-about.adoc index 3f7309f..b0d8fbe 100644 --- a/modules/ROOT/pages/epel-about.adoc +++ b/modules/ROOT/pages/epel-about.adoc @@ -46,11 +46,11 @@ method to build support and community around particular software needs. [[community_perspective]] === Community Perspective -Many members of the Fedora community are also users/administrators of -enterprise-Linux based distributions that are derived from Fedora, such -as RHEL and CentOS. Everyone has their own reasons for promoting a -particular piece of software. EPEL packages are the best way to gain -users and support from enterprise Linux users. +Many members of the Fedora community +are also users/administrators of Enterprise Linux distributions that are derived from Fedora, +such as CentOS Stream and RHEL. +Everyone has their own reasons for promoting a particular piece of software. +EPEL packages are the best way to gain users and support from Enterprise Linux users. [[isvihv_perspective]] === ISV/IHV Perspective diff --git a/modules/ROOT/pages/epel-faq.adoc b/modules/ROOT/pages/epel-faq.adoc index ea771c3..0cb5d2f 100644 --- a/modules/ROOT/pages/epel-faq.adoc +++ b/modules/ROOT/pages/epel-faq.adoc @@ -6,10 +6,13 @@ include::partial$attributes.adoc[] [[what_is_epel]] === What is EPEL? -EPEL (Extra Packages for Enterprise Linux) is a volunteer-based -community effort from the Fedora project to create a repository of -high-quality add-on packages that complement the Fedora-based Red Hat -Enterprise Linux (RHEL) and its compatible spin-offs, such as CentOS. +Extra Packages for Enterprise Linux (EPEL) is an initiative within the +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). +EPEL packages will also likely work with other distributions +that target RHEL compatibility. As part of the Fedora packaging community, EPEL packages are 100% free/libre open source software (FLOSS). @@ -38,20 +41,19 @@ engineers are involved as maintainers and leaders but there are no commercial support contracts or service level agreements provided by Red Hat for packages in EPEL. -[[which_releases_of_red_hat_enterprise_linux_or_derivatives_does_epel_project_provides_packages_for]] -=== Which releases of Red Hat Enterprise Linux or derivatives does EPEL project provides packages for? +[[which_distributions_and_releases_does_epel_provides_packages_for]] +=== Which distributions and releases does EPEL provides packages for? -EPEL project provides add-on packages for Red Hat Enterprise Linux 8, 7, 6, -and 5 releases and compatible derivatives (e.g., -https://www.centos.org[CentOS]). Packages for Red Hat Enterprise Linux 4, -3 and 2 are not provided because these releases are at End of Life per -Red Hat's https://www.redhat.com/security/updates/errata/[errata support -policy]. Also, over time, Fedora diverges from older RHEL releases, and -it can become more difficult to maintain packages that must build -against the older RHEL versions. +EPEL provides packages for CentOS Stream 9, +Red Hat Enterprise Linux 9, +and Red Hat Enterprise Linux 8. +EPEL packages will also likely work with other distributions +that target RHEL compatibility. +Packages for earlier versions of CentOS Stream and RHEL are no longer provided +because these versions are end of life. -[[how_is_epel_different_from_other_third_party_repositories_for_rhel_and_derivatives]] -=== How is EPEL different from other third party repositories for RHEL and derivatives? +[[how_is_epel_different_from_other_third_party_repositories_for_rhel]] +=== How is EPEL different from other third party repositories for RHEL? * EPEL packages are in most cases built or derived from the equivalent ones in Fedora repository and maintained by the same people. It has also @@ -66,18 +68,8 @@ volunteer community members working together to maintain the repository. * EPEL only provides free and open source software unencumbered by patents or any legal issues. -See also https://wiki.centos.org/AdditionalResources/Repositories[CentOS -FAQ] on alternate repositories. - == Packages -[[are_epel_packages_available_only_for_rhel_or_also_for_compatible_derivatives]] -=== Are EPEL packages available only for RHEL or also for compatible derivatives? - -Packages are freely available and it is an *explicit goal of the project -to make sure they are usable for RHEL-based distributions such as CentOS -and Scientific Linux.* - [[does_epel_replace_packages_provided_within_red_hat_enterprise_linux]] === Does EPEL replace packages provided within Red Hat Enterprise Linux? @@ -296,9 +288,9 @@ signed with a particular key as well as which repo they came from. [[is_epel_upstream_or_an_official_package_repository_like_fedora_extras_was]] === Is EPEL "upstream" or "an official package repository" (like Fedora Extras was)? -EPEL is just one of several add on repositories with RPM packages for -RHEL and derivates. It is not an official repository. The different -repositories serve different user bases or follow different ideas. +EPEL is just one of several add-on repositories with RPM packages for RHEL. +It is not an official repository. +The different repositories serve different user bases or follow different ideas. Just like RHEL itself, EPEL in reality is more a "downstream" in the sense that Fedora is upstream and EPEL, just like Red Hat, takes @@ -411,6 +403,14 @@ 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] +You can also check the package source repos in the +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, +that means it was removed during development of that RHEL version +and is thus eligible for EPEL. + [[i_want_to_build_packages_for_epel_but_some_of_my_packages_dependencies_are_not_available_in_epel____or____id_like_to_see_a_fedora_package_in_epel_that_is_not_yet_available_there]] === I want to build packages for EPEL but some of my packages dependencies are not available in EPEL -- or -- I'd like to see a Fedora package in EPEL that is not yet available there @@ -442,7 +442,8 @@ repository. 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://wiki.centos.org/ReportBugs[CentOS wiki]. +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]. ** Be sure to say that it is impacting an EPEL build, and which package it is impacting. @@ -527,15 +528,14 @@ repositories and encourages maintainers to do so whenever possible. [[what_about_compatibility_with_other_third_party_repositories]] === What about compatibility with other third party repositories? -Mixing different RPM repositories that were not designed to be mixed can -lead to incompatibilities that often result in dependency resolution -problems in yum. Sometimes it even happens that software is not working -as expected if libraries and applications come from different -repositories. EPEL is designed as an add-on repository for RHEL and -compatible derivatives. The best way to avoid problems is to avoid -mixing EPEL with other third party repositories that have conflicting -packages on the same system. Some people nevertheless do it and the yum -priorities plugin can help to avoid the worst problems. +Mixing different RPM repositories that were not designed to be mixed +can lead to incompatibilities that often result in dependency resolution problems in yum. +Sometimes it even happens that software is not working as expected +if libraries and applications come from different repositories. +EPEL is designed as an add-on repository for RHEL. +The best way to avoid problems is to avoid mixing EPEL with other third party repositories +that have conflicting packages on the same system. +Some people nevertheless do it and the yum priorities plugin can help to avoid the worst problems. If you encounter a problem where packages from EPEL are incompatible with another repository, or lead yum or up2date to bail out during diff --git a/modules/ROOT/pages/epel-package-maintainer-generic-description.adoc b/modules/ROOT/pages/epel-package-maintainer-generic-description.adoc index 1f79092..bde8a07 100644 --- a/modules/ROOT/pages/epel-package-maintainer-generic-description.adoc +++ b/modules/ROOT/pages/epel-package-maintainer-generic-description.adoc @@ -44,8 +44,7 @@ problems, fix bugs, and introduce new features. The EPEL project synchronizes packages with specific release of Red Hat Enterprise Linux. To maintain an EPEL package, you must help maintain the synchronization against at least the one specific version of Red Hat -Enterprise Linux. You can do this using Red Hat's build or any other -build, such as CentOS. +Enterprise Linux. [[job_duties]] === Job Duties diff --git a/modules/ROOT/pages/epel-packaging-examples.adoc b/modules/ROOT/pages/epel-packaging-examples.adoc index 86b8d50..037f149 100644 --- a/modules/ROOT/pages/epel-packaging-examples.adoc +++ b/modules/ROOT/pages/epel-packaging-examples.adoc @@ -24,7 +24,7 @@ This is an example workflow. * Download the source rpm corresponding to the latest released RHEL build * *fedpkg import * ** fedpkg import /tmp/pycairo-1.20.0-4.el9.src.rpm -* *fedpkg commit -m "import from CentOS srpm"* +* *fedpkg commit -m "import from CentOS Stream srpm"* * *git mv .spec -epel.spec* ** git mv pycairo.spec pycairo-epel.spec * *fedpkg commit -m "rename spec file"* diff --git a/modules/ROOT/pages/epel-policy-missing-sub-packages.adoc b/modules/ROOT/pages/epel-policy-missing-sub-packages.adoc index 3eaad58..e19f1af 100644 --- a/modules/ROOT/pages/epel-policy-missing-sub-packages.adoc +++ b/modules/ROOT/pages/epel-policy-missing-sub-packages.adoc @@ -46,10 +46,13 @@ 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. 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://wiki.centos.org/ReportBugs[CentOS wiki]. +* To initiate this process, +please file an issue in 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]. * Be sure to say that it is impacting an EPEL build, and which package it is impacting. .... diff --git a/modules/ROOT/pages/epel-policy.adoc b/modules/ROOT/pages/epel-policy.adoc index 83376ee..32a8487 100644 --- a/modules/ROOT/pages/epel-policy.adoc +++ b/modules/ROOT/pages/epel-policy.adoc @@ -109,9 +109,6 @@ changes the ABI. Packages in the testing repo for 2 weeks are automatically promoted to stable. Packages with sufficient karma are also promoted to stable. Update candidates that aren't pushed to stable after 6 months are eligible to be removed by Release Engineering. -When a new quarterly update is released, EPEL will wait until the CentOS -version of that update is available. - For more information about updating EPEL packages, including minimum testing time for packages, refer to the xref:epel-policy-updates.adoc[EPEL Updates Policy]. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 3680ab9..b1c3f24 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -18,11 +18,11 @@ Learn more about getting started using EPEL on the following page: [[what_is_extra_packages_for_enterprise_linux_or_epel]] == What is Extra Packages for Enterprise Linux (or EPEL)? -Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special -Interest Group that creates, maintains, and manages a high quality set -of additional packages for Enterprise Linux, including, but not limited -to, https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/index.html[Red Hat Enterprise Linux] (RHEL), -CentOS, Scientific Linux (SL), Oracle Linux (OL), AlmaLinux (AL) and Rocky Linux (RL). +Extra Packages for Enterprise Linux (EPEL) is an initiative within the +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). EPEL packages are usually based on their Fedora counterparts and should not conflict with or replace packages in the base Enterprise Linux distributions.