[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?
On Wednesday, August 31, 2022 Troy Dawson wrote: > EPEL2RHEL is part of the RHEL 8 and 9 new package workflow. When a RHEL > maintainer wants to add a package to RHEL 8 or 9 they start a "new package > workflow". There are several automations that happen when they start that > workflow. One of them is checking if the package is already in epel. If > it is, it creates a bugzilla against that package, and links that bug > against the EPEL2RHEL tracker. [1] > Remember, this check currently happens at the beginning of the new package > workflow. Before a package has been branched, built, or put into testing > repos. I think this whole process should be automated. File bugs that say "Heads up: your package will be automatically retired after the release of RHEL X.X" and provide some explanation. This will have multiple benefits: 1. Saying "you'll have to do something in six months, but it'll be bad if you do it now" is quite difficult to follow. 2. We can send out one announcement to epel-announce about which packages are going to be retired and when that'll happen, instead of retiring packages in a piecemeal manner. 3. The maintainers won't have to remember to do it. 4. If we find out that a package is buildroot only, then we'll close the bug and exclude it from the automatic retiring. -- Best, Maxwell G (@gotmax23) Pronouns: He/Him/His ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: Proposal: Dropping modules from EPEL-8. Not adding modules to EPEL-9
On Thu, 1 Sept 2022 at 12:25, Troy Dawson wrote: > > > On Thu, Sep 1, 2022 at 12:19 AM Miro Hrončok wrote: > >> On 31. 08. 22 23:08, Stephen Smoogen 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 it is time to say this experiment with modules in EPEL >> has not >> > worked and focus resources on what does work. I would like to propose >> that >> > modular support is removed from EPEL by January 2023. >> > >> > Steps: >> > 1. Approval of this proposal by the EPEL Steering committee and any >> other ones >> > required. >> > 2. Announcement of end of life to various lists. >> > > 2.5 - move epel-modular.repo and epel-testing-modular.repo to it's own > sub-package of epel-repos-modular > > >> > 3. Archiving of the modules on XYZ date to >> /pub/archive/epel/8.-MM/Modular >> > and pointing mirrormanager to that for that >> > 4. Make changes in bodhi to turn off reporting about modules for EL8. >> > 5. Make changes in MBS configs to turn off building modules for EL8. >> > 6. Make changes in PDC for EL8 modules >> > 7. Make changes in compose scripts and tools to no longer cover EPEL-8 >> modules >> > 8. Remove epel-8 modules from /pub/epel/8 >> > 9. Announce closure of this proposal and any lessons learned. > > > 10. Drop > https://src.fedoraproject.org/rpms/epel-release/blob/epel8/f/epel-testing-modular.repo > from epel-repos-modular > > I agree with Miro and your changes and will put a ticket into the pagure to start the ball rolling. > Troy > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: Proposal: Dropping modules from EPEL-8. Not adding modules to EPEL-9
On Thu, Sep 1, 2022 at 12:19 AM Miro Hrončok wrote: > On 31. 08. 22 23:08, Stephen Smoogen 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 it is time to say this experiment with modules in EPEL has > not > > worked and focus resources on what does work. I would like to propose > that > > modular support is removed from EPEL by January 2023. > > > > Steps: > > 1. Approval of this proposal by the EPEL Steering committee and any > other ones > > required. > > 2. Announcement of end of life to various lists. > 2.5 - move epel-modular.repo and epel-testing-modular.repo to it's own sub-package of epel-repos-modular > > 3. Archiving of the modules on XYZ date to > /pub/archive/epel/8.-MM/Modular > > and pointing mirrormanager to that for that > > 4. Make changes in bodhi to turn off reporting about modules for EL8. > > 5. Make changes in MBS configs to turn off building modules for EL8. > > 6. Make changes in PDC for EL8 modules > > 7. Make changes in compose scripts and tools to no longer cover EPEL-8 > modules > > 8. Remove epel-8 modules from /pub/epel/8 > > 9. Announce closure of this proposal and any lessons learned. 10. Drop https://src.fedoraproject.org/rpms/epel-release/blob/epel8/f/epel-testing-modular.repo from epel-repos-modular Troy ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cf9b662b60 tcpreplay-4.4.2-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing python-apprise-1.0.0-1.el7 python-colcon-cmake-0.2.27-1.el7 python-colcon-notification-0.2.14-1.el7 Details about builds: python-apprise-1.0.0-1.el7 (FEDORA-EPEL-2022-0d904edce5) A simple wrapper to many popular notification services used today Update Information: Updated to v1.0.0 ChangeLog: * Sat Aug 6 2022 Chris Caron - 1.0.0-1 - Updated to v1.0.0 * Fri Jul 22 2022 Fedora Release Engineering - 0.9.9-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Wed Jun 15 2022 Python Maint - 0.9.9-2 - Rebuilt for Python 3.11 python-colcon-cmake-0.2.27-1.el7 (FEDORA-EPEL-2022-84eca73e4f) Extension for colcon to support CMake packages Update Information: Update to `colcon-cmake` 0.2.27 ChangeLog: * Wed Aug 31 2022 Scott K Logan - 0.2.27-1 - Update to 0.2.27 (rhbz#2123074) References: [ 1 ] Bug #2123074 - python-colcon-cmake-0.2.27 is available https://bugzilla.redhat.com/show_bug.cgi?id=2123074 python-colcon-notification-0.2.14-1.el7 (FEDORA-EPEL-2022-a8ad352036) Extension for colcon to provide status notifications Update Information: Update to `colcon-notification` 0.2.14 ChangeLog: * Wed Aug 31 2022 Scott K Logan - 0.2.14-1 - Update to 0.2.14 (rhbz#2123069) References: [ 1 ] Bug #2123069 - python-colcon-notification-0.2.14 is available https://bugzilla.redhat.com/show_bug.cgi?id=2123069 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 43 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-89ad385971 chromium-103.0.5060.114-1.el8 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-00b4829e45 tcpreplay-4.4.2-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing clifm-1.7-2.el8 python-apprise-1.0.0-1.el8 python-colcon-cmake-0.2.27-1.el8 python-colcon-notification-0.2.14-1.el8 Details about builds: clifm-1.7-2.el8 (FEDORA-EPEL-2022-4c4b3cb4a1) Shell-like, command line terminal file manager Update Information: update package description initial package build ChangeLog: * Tue Aug 16 2022 Jonathan Wright - 1.7-2 - adjust description per upstream request - https://github.com/leo-arch/clifm/issues/154#issuecomment-1233102727 * Tue Aug 16 2022 Jonathan Wright - 1.7-1 - Initial package build - rhbz#2118835 python-apprise-1.0.0-1.el8 (FEDORA-EPEL-2022-d97d1f9941) A simple wrapper to many popular notification services used today Update Information: Updated to v1.0.0 ChangeLog: * Sat Aug 6 2022 Chris Caron - 1.0.0-1 - Updated to v1.0.0 * Fri Jul 22 2022 Fedora Release Engineering - 0.9.9-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Wed Jun 15 2022 Python Maint - 0.9.9-2 - Rebuilt for Python 3.11 python-colcon-cmake-0.2.27-1.el8 (FEDORA-EPEL-2022-5a0dde596a) Extension for colcon to support CMake packages Update Information: Update to `colcon-cmake` 0.2.27 ChangeLog: * Wed Aug 31 2022 Scott K Logan - 0.2.27-1 - Update to 0.2.27 (rhbz#2123074) References: [ 1 ] Bug #2123074 - python-colcon-cmake-0.2.27 is available https://bugzilla.redhat.com/show_bug.cgi?id=2123074 python-colcon-notification-0.2.14-1.el8 (FEDORA-EPEL-2022-a44e3f7068) Extension for colcon to provide status notifications Update Information: Update to `colcon-notification` 0.2.14 ChangeLog: * Wed Aug 31 2022 Scott K Logan - 0.2.14-1 - Update to 0.2.14 (rhbz#2123069) References: [ 1 ] Bug #2123069 - python-colcon-notification-0.2.14 is available https://bugzilla.redhat.com/show_bug.cgi?id=2123069 ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?
On 01. 09. 22 0:19, Troy Dawson wrote:
** Solution(s)
A - At the very least, we need to change the wording of the bugs. I am
proposing the following
Subject: Remove from epel9 when rhel 9.1 is released
Comment: This package is being added to RHEL 9.1 at the next minor release.
After the next RHEL minor release, please verify this package was released in
RHEL, and if so remove it from epel9.
Yes please. Ideally, even add a reproducer that verifies this ("go to X and
search for the package name" or "run this repoquery" or even "go to this
documentation page to check it")
B - If possible, move the EPEL2RHEL check to later in the development cycle. I
would like it to be in the step where the packages get added to BaseOS,
AppStream, or CRB. That way we would know it isn't going to be a BuildRoot
only package, and it would reduce the time the bugs sit waiting.
I don't know if this is possible, but I'm going to ask.
Agreed. It could even say which (sub)packages are being added and link to the
appropriate documentation in case some of the EPEL subpackages need to be split
into a spearate component.
C - ?? What if we only created the bugs on the tracker itself, and not the
individual packages ??
Would that be a good thing? Or would it irritate the maintainers?
What do you mean by this? I don't understand it. File it against the
distribution? If there is a dedicated (and educated) person/team who would deal
with this at all RHEL release boundaries, than this makes sense. Otherwise it
just hides this information from the EPEL maintainers.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: Proposal: Dropping modules from EPEL-8. Not adding modules to EPEL-9
On 31. 08. 22 23:08, Stephen Smoogen 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 it is time to say this experiment with modules in EPEL has not worked and focus resources on what does work. I would like to propose that modular support is removed from EPEL by January 2023. Steps: 1. Approval of this proposal by the EPEL Steering committee and any other ones required. 2. Announcement of end of life to various lists. 3. Archiving of the modules on XYZ date to /pub/archive/epel/8.-MM/Modular and pointing mirrormanager to that for that 4. Make changes in bodhi to turn off reporting about modules for EL8. 5. Make changes in MBS configs to turn off building modules for EL8. 6. Make changes in PDC for EL8 modules 7. Make changes in compose scripts and tools to no longer cover EPEL-8 modules 8. Remove epel-8 modules from /pub/epel/8 9. Announce closure of this proposal and any lessons learned. 10. Drop https://src.fedoraproject.org/rpms/epel-release/blob/epel8/f/epel-testing-modular.repo -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
