[EPEL-devel] Re: EPEL: packaging multiple versions and compat packages
On Monday, September 5, 2022 Mark E. Fuller wrote: > Can someone point me to a good resource on how (if permitted) I can make > appropriate compat(?) packages to allow for two major versions of the > same package to be available? > Is this allowed for EPEL? You can package compat packages as long as they don't conflict with anything in RHEL. EPEL packages may conflict with other EPEL packages, however. -- Maxwell G (@gotmax23) Pronouns: He/Him/His signature.asc Description: This is a digitally signed message part. ___ 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] EPEL: packaging multiple versions and compat packages
Hi all, Can someone point me to a good resource on how (if permitted) I can make appropriate compat(?) packages to allow for two major versions of the same package to be available? Is this allowed for EPEL? Thanks -- Mark E. Fuller, Ph.D. ful...@fedoraproject.org ful...@mefuller.dev @fuller:fedora.im @fuller:one.ems.host https://www.stossrohr.net PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60 ___ 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 Mon, 2022-09-05 at 11:33 +0200, Dominik 'Rathann' Mierzejewski wrote: > It would be really nice if the wording of the bug could contain some > kind of a "thank you" note to the EPEL maintainers of the package in > question. Not everyone will understand this process as "great, I > don't > have to maintain package X anymore, Red Hat will be doing that for me > from now on". Some folks may take it as "Oh no! Red Hat is taking > away > my toy! Why?!" Ideally, there should still be a way for EPEL > maintainer(s) to continue contributing to the RHEL package. This is a great idea. Maybe we could have a link to a doc that explains what's going on in more details and how to contribute to the package once it's in RHEL ? Cheers Davide ___ 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: Adding Package to side-tag
On Sun, 2022-09-04 at 17:18 -0700, Kevin Fenzi wrote: > On Sat, Sep 03, 2022 at 08:32:47PM +1000, Frank Crawford wrote: > > > > The document I used > > was https://docs.fedoraproject.org/en-US/package- > > maintainers/Package_Update_Guide/#multiple_packages > > > > It was the only place I could find that really talked about side- > > tags, > > and wait-repo looks only mentioned in passing. Once you know it is > > needed it is more obvious, but not if you haven't used them much > > before. > > Well, it does say: > > "The latter is important if any builds depend on previous ones in the > side tag. > Use koji wait-repo --build to ensure that > the respective > build is available in the build root for subsequent builds. " > > But if you can see a way to be more clear there, perhaps you could > put > in a PR? I'll see what I can do, but the issue is more about understanding what is happening in the background than just the wording. Now seeing it fail it is obvious that each side-tag has its own repo, and this is waiting for it to be created, but prior to sitting back and thinking what has to go on the term "wait-repo" is just an extra step. What seems to be really missing is some details of what is happening in the background rather than a list of commands that are important. As I said earlier, there seems to be very little documentation anywhere, on what a side-tag actually is, or what it does. Naively, I assumed just added an extra tag, and that is all. > kevin Regards Frank ___ 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 Friday, 02 September 2022 at 18:25, Kevin Fenzi wrote: > On Thu, Sep 01, 2022 at 12:12:07PM -0500, Maxwell G via epel-devel wrote: > > 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. > > I really like this approach... :) It would be really nice if the wording of the bug could contain some kind of a "thank you" note to the EPEL maintainers of the package in question. Not everyone will understand this process as "great, I don't have to maintain package X anymore, Red Hat will be doing that for me from now on". Some folks may take it as "Oh no! Red Hat is taking away my toy! Why?!" Ideally, there should still be a way for EPEL maintainer(s) to continue contributing to the RHEL package. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ 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 47 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-89ad385971 chromium-103.0.5060.114-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-83ed996f1e rubygem-rack-2.2.4-1.el8 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ebbc78f3cb libapreq2-2.17-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing mold-1.4.2-1.el8 mup-7.0-1.el8 Details about builds: mold-1.4.2-1.el8 (FEDORA-EPEL-2022-a941d2abcf) A Modern Linker Update Information: Bump version to 1.4.2 ChangeLog: * Sun Sep 4 2022 Christoph Erhardt - 1.4.2-1 - Bump version to 1.4.2 - Refresh patch mup-7.0-1.el8 (FEDORA-EPEL-2022-8a71d776ba) A music notation program that can also generate MIDI files Update Information: Update to 7.0 ChangeLog: * Sun Sep 4 2022 Greg Bailey - 7.0-1 - Update to 7.0 - noteleft string - mensural symbols and centered stems - improved measuration time signature sizing when used with printedtime - expression eval macros - string() function - shapes context * Fri Jul 22 2022 Fedora Release Engineering - 6.7-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Thu Jan 20 2022 Fedora Release Engineering - 6.7-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Thu Jul 22 2021 Fedora Release Engineering - 6.7-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Tue Jan 26 2021 Fedora Release Engineering - 6.7-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Tue Jul 28 2020 Fedora Release Engineering - 6.7-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Wed Jan 29 2020 Fedora Release Engineering - 6.7-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild ___ 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 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b86f845eb8 libapreq2-2.17-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing mup-7.0-1.el7 Details about builds: mup-7.0-1.el7 (FEDORA-EPEL-2022-0cb0fe56f9) A music notation program that can also generate MIDI files Update Information: Update to 7.0 ChangeLog: * Sun Sep 4 2022 Greg Bailey - 7.0-1 - Update to 7.0 - noteleft string - mensural symbols and centered stems - improved measuration time signature sizing when used with printedtime - expression eval macros - string() function - shapes context * Fri Jul 22 2022 Fedora Release Engineering - 6.7-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Thu Jan 20 2022 Fedora Release Engineering - 6.7-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Thu Jul 22 2021 Fedora Release Engineering - 6.7-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Tue Jan 26 2021 Fedora Release Engineering - 6.7-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Tue Jul 28 2020 Fedora Release Engineering - 6.7-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Wed Jan 29 2020 Fedora Release Engineering - 6.7-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild ___ 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 9 updates-testing report
The following builds have been pushed to Fedora EPEL 9 updates-testing mold-1.4.2-1.el9 mup-7.0-1.el9 Details about builds: mold-1.4.2-1.el9 (FEDORA-EPEL-2022-1dd1cd73e4) A Modern Linker Update Information: Bump version to 1.4.2 ChangeLog: * Sun Sep 4 2022 Christoph Erhardt - 1.4.2-1 - Bump version to 1.4.2 - Refresh patch mup-7.0-1.el9 (FEDORA-EPEL-2022-526c3fb1aa) A music notation program that can also generate MIDI files Update Information: Update to 7.0 ChangeLog: * Sun Sep 4 2022 Greg Bailey - 7.0-1 - Update to 7.0 - noteleft string - mensural symbols and centered stems - improved measuration time signature sizing when used with printedtime - expression eval macros - string() function - shapes context ___ 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
