When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked.
At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work.
Schedule of EPEL 8 Module Retirement: Next Week: - epel-release will be updated. -- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it
October 31 2022: - The EPEL 8 modules will be archived and removed. -- The mirror manager will be pointed to the archive. - Packagers will no longer be able to build EPEL 8 modules.
After October 31st (Actual date to be determined): - epel-release will be updated again. -- epel-modular repo configs will be removed.
Questions and Answers:
Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them.
Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin
EPEL Steering Committee
On Wed, Sep 28, 2022 at 6:10 PM Troy Dawson tdawson@redhat.com wrote:
When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked.
At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work.
This was my conclusion with the RPMs I publish, which replace RHEL RPMs and would not be accepted for EPEL. But dear lord, the modularity has been a problem and I'm delighted it's being discarded for EPEL.
Schedule of EPEL 8 Module Retirement: Next Week:
- epel-release will be updated.
-- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it
October 31 2022:
- The EPEL 8 modules will be archived and removed.
-- The mirror manager will be pointed to the archive.
- Packagers will no longer be able to build EPEL 8 modules.
After October 31st (Actual date to be determined):
- epel-release will be updated again.
-- epel-modular repo configs will be removed.
Questions and Answers:
Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them.
Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin
EPEL Steering Committee
[1] - https://pagure.io/epel/issue/198 _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Sep 28, 2022 at 3:10 PM Troy Dawson tdawson@redhat.com wrote:
When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked.
At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work.
Schedule of EPEL 8 Module Retirement: Next Week:
- epel-release will be updated.
-- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it
October 31 2022:
- The EPEL 8 modules will be archived and removed.
-- The mirror manager will be pointed to the archive.
- Packagers will no longer be able to build EPEL 8 modules.
After October 31st (Actual date to be determined):
- epel-release will be updated again.
-- epel-modular repo configs will be removed.
Questions and Answers:
Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them.
Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin
EPEL Steering Committee
Question: Many Enterprise customers need time for a transition like this. Can the transition date be pushed back? Answer: This will have to be voted on by the EPEL Steering Committee. The answer is likely yes, but I won't give a firm answer until it's been discussed and voted on.
There has been a schedule update to the epel8 modularity removal.
October 31, 2022 - The updated epel-release will be pushed to epel8 stable -- This sets "enabled = 0" for epel-modular, if you haven't already changed your config.
February 15, 2023 - The EPEL 8 modules will be archived and removed. -- The mirror manager will be pointed to the archive.
* Question:Why was the final archive moved to February 15th. * Answer1: EPEL is made to help Enterprise users. Many Enterprise users are already in an end of the year freeze. This will give them time to plan, test, and implement any changes they might face. * Answer2: Because February 14th was voted down by our significant others.
EPEL Steering Committee
On Wed, Sep 28, 2022 at 3:10 PM Troy Dawson tdawson@redhat.com wrote:
When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked.
At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work.
Schedule of EPEL 8 Module Retirement: Next Week:
- epel-release will be updated.
-- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it
October 31 2022:
- The EPEL 8 modules will be archived and removed.
-- The mirror manager will be pointed to the archive.
- Packagers will no longer be able to build EPEL 8 modules.
After October 31st (Actual date to be determined):
- epel-release will be updated again.
-- epel-modular repo configs will be removed.
Questions and Answers:
Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them.
Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin
EPEL Steering Committee
-
Nico Kadel-Garcia -
Troy Dawson