[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?
On Thu, 2023-03-16 at 16:05 -0700, Troy Dawson wrote: > > > On Thu, Mar 16, 2023 at 3:43 PM Kevin Fenzi wrote: > > On Thu, Mar 16, 2023 at 03:10:23PM -0700, Troy Dawson wrote: > > > > > > This is what I have on my ticket. Respond soon (by tomorrow end > > > of day) if > > > you think I need changes. > > > > > > Subject: > > > Notice: will be automatically retired from epel > > > when RHEL > > > . is released > > > > > > Comment: > > > Thank you for your work maintaining in epel. > > > This package > > > has been considered important enough to Red Hat's customers that > > > Red Hat > > > has decided to promote it to be an official part of RHEL. It > > > will be part > > > of RHEL .. When that is released, EPEL automation > > > will > > > remove from epel. > > > > That looks pretty good, but I might suggest adding something more > > explicit at the end: > > > > Note that this issue is purely informational, you do not need to > > take any > > actions at this time. > > > > But perhaps thats overkill. ;) > > > > kevin > > > > > It's slight overkill, but you are correct, they might think they have > to do something. > I have changed the last sentence to be > > When that is released, EPEL automation will remove from > EPEL and close this bug. > > Troy I'd consider something in a final paragraph that says "something like": No action is required from you at this time. Having an explicit "non-call to action" int its own paragraph may help folks feel more comfortable that they know what to expect and what they do/do not need to do. Pat ___ 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 Thu, Mar 16, 2023 at 7:08 PM Troy Dawson wrote: > > On Thu, Mar 16, 2023 at 3:35 PM Neal Gompa wrote: >> >> On Thu, Mar 16, 2023 at 6:10 PM Troy Dawson wrote: >> > >> > On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson wrote: >> >> >> >> >> >> >> >> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster >> >> wrote: >> >>> >> >>> On Mon, Sep 5, 2022 at 9:33 AM 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. >> >>> >> >>> Perhaps add something like (wordsmithed by someone >> >>> competent in such things): >> >>> >> >>> "The package you have been maintaining in EPEL is now >> >>> considered important enough to a large enough part of our >> >>> customers that Red Hat has decided to promote it to being >> >>> an officially supported part of the product" >> >> >> >> >> >> I like that idea. It's much more positive. A nice "Thank you for doing >> >> this in EPEL" type of feel. >> >> >> >> Troy >> > >> > >> > This is what I have on my ticket. Respond soon (by tomorrow end of day) >> > if you think I need changes. >> > >> > Subject: >> > Notice: will be automatically retired from epel when RHEL >> > . is released >> > >> > Comment: >> > Thank you for your work maintaining in epel. This >> > package has been considered important enough to Red Hat's customers that >> > Red Hat has decided to promote it to be an official part of RHEL. It will >> > be part of RHEL .. When that is released, EPEL automation >> > will remove from epel. >> > >> >> That is pretty well worded, though you can just use "EPEL " >> instead of "epel". >> > > I was debating whether to use capital letters or not. I agree with you, I > think it does look better, and I have capital RHEL. > With the bit I added for Kevin, here is what I currently have > > Subject: > Notice: will be automatically retired from EPEL when RHEL > . is released > > Comment: > > Thank you for your work maintaining in EPEL . This package > has been considered important enough to Red Hat's customers that Red Hat has > decided to promote it to be an official part of RHEL. It will be part of > RHEL .. When that is released, EPEL automation will remove > from EPEL and close this bug. > That looks great! -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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 Thu, Mar 16, 2023 at 3:35 PM Neal Gompa wrote: > On Thu, Mar 16, 2023 at 6:10 PM Troy Dawson wrote: > > > > On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson wrote: > >> > >> > >> > >> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster < > gary.buhrmas...@gmail.com> wrote: > >>> > >>> On Mon, Sep 5, 2022 at 9:33 AM 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. > >>> > >>> Perhaps add something like (wordsmithed by someone > >>> competent in such things): > >>> > >>> "The package you have been maintaining in EPEL is now > >>> considered important enough to a large enough part of our > >>> customers that Red Hat has decided to promote it to being > >>> an officially supported part of the product" > >> > >> > >> I like that idea. It's much more positive. A nice "Thank you for > doing this in EPEL" type of feel. > >> > >> Troy > > > > > > This is what I have on my ticket. Respond soon (by tomorrow end of day) > if you think I need changes. > > > > Subject: > > Notice: will be automatically retired from epel when > RHEL . is released > > > > Comment: > > Thank you for your work maintaining in epel. This > package has been considered important enough to Red Hat's customers that > Red Hat has decided to promote it to be an official part of RHEL. It will > be part of RHEL .. When that is released, EPEL automation > will remove from epel. > > > > That is pretty well worded, though you can just use "EPEL " > instead of "epel". > > I was debating whether to use capital letters or not. I agree with you, I think it does look better, and I have capital RHEL. With the bit I added for Kevin, here is what I currently have Subject: Notice: will be automatically retired from EPEL when RHEL . is released Comment: Thank you for your work maintaining in EPEL . This package has been considered important enough to Red Hat's customers that Red Hat has decided to promote it to be an official part of RHEL. It will be part of RHEL .. When that is released, EPEL automation will remove from EPEL and close this bug. ___ 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 Thu, Mar 16, 2023 at 3:43 PM Kevin Fenzi wrote: > On Thu, Mar 16, 2023 at 03:10:23PM -0700, Troy Dawson wrote: > > > > This is what I have on my ticket. Respond soon (by tomorrow end of day) > if > > you think I need changes. > > > > Subject: > > Notice: will be automatically retired from epel when > RHEL > > . is released > > > > Comment: > > Thank you for your work maintaining in epel. This > package > > has been considered important enough to Red Hat's customers that Red Hat > > has decided to promote it to be an official part of RHEL. It will be > part > > of RHEL .. When that is released, EPEL automation will > > remove from epel. > > That looks pretty good, but I might suggest adding something more > explicit at the end: > > Note that this issue is purely informational, you do not need to take any > actions at this time. > > But perhaps thats overkill. ;) > > kevin > It's slight overkill, but you are correct, they might think they have to do something. I have changed the last sentence to be When that is released, EPEL automation will remove from EPEL and close this bug. 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] Re: EPEL2RHEL - New Wording? - New Workflow?
On Thu, Mar 16, 2023 at 03:10:23PM -0700, Troy Dawson wrote: > > This is what I have on my ticket. Respond soon (by tomorrow end of day) if > you think I need changes. > > Subject: > Notice: will be automatically retired from epel when RHEL > . is released > > Comment: > Thank you for your work maintaining in epel. This package > has been considered important enough to Red Hat's customers that Red Hat > has decided to promote it to be an official part of RHEL. It will be part > of RHEL .. When that is released, EPEL automation will > remove from epel. That looks pretty good, but I might suggest adding something more explicit at the end: Note that this issue is purely informational, you do not need to take any actions at this time. But perhaps thats overkill. ;) kevin signature.asc Description: PGP signature ___ 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 Thu, Mar 16, 2023 at 6:10 PM Troy Dawson wrote: > > On Mon, Feb 20, 2023 at 6:33 AM Troy Dawson wrote: >> >> >> >> On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster >> wrote: >>> >>> On Mon, Sep 5, 2022 at 9:33 AM 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. >>> >>> Perhaps add something like (wordsmithed by someone >>> competent in such things): >>> >>> "The package you have been maintaining in EPEL is now >>> considered important enough to a large enough part of our >>> customers that Red Hat has decided to promote it to being >>> an officially supported part of the product" >> >> >> I like that idea. It's much more positive. A nice "Thank you for doing >> this in EPEL" type of feel. >> >> Troy > > > This is what I have on my ticket. Respond soon (by tomorrow end of day) if > you think I need changes. > > Subject: > Notice: will be automatically retired from epel when RHEL > . is released > > Comment: > Thank you for your work maintaining in epel. This package > has been considered important enough to Red Hat's customers that Red Hat has > decided to promote it to be an official part of RHEL. It will be part of > RHEL .. When that is released, EPEL automation will remove > from epel. > That is pretty well worded, though you can just use "EPEL " instead of "epel". -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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, Feb 20, 2023 at 6:33 AM Troy Dawson wrote: > > > On Sun, Feb 19, 2023 at 6:25 PM Gary Buhrmaster > wrote: > >> On Mon, Sep 5, 2022 at 9:33 AM 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. >> >> Perhaps add something like (wordsmithed by someone >> competent in such things): >> >> "The package you have been maintaining in EPEL is now >> considered important enough to a large enough part of our >> customers that Red Hat has decided to promote it to being >> an officially supported part of the product" >> > > I like that idea. It's much more positive. A nice "Thank you for doing > this in EPEL" type of feel. > > Troy > This is what I have on my ticket. Respond soon (by tomorrow end of day) if you think I need changes. Subject: Notice: will be automatically retired from epel when RHEL . is released Comment: Thank you for your work maintaining in epel. This package has been considered important enough to Red Hat's customers that Red Hat has decided to promote it to be an official part of RHEL. It will be part of RHEL .. When that is released, EPEL automation will remove from epel. 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 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7b23e5a4b3 chromium-111.0.5563.64-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing eggdrop-1.9.5-1.el7 lua-sec-1.3.0-1.el7 rpminspect-data-centos-1.2-1.el7 uglify-js-3.17.4-1.el7 Details about builds: eggdrop-1.9.5-1.el7 (FEDORA-EPEL-2023-7bcbf226b6) World's most popular Open Source IRC bot Update Information: # Eggdrop v1.9.5 ## General changes - Implemented a workaround for a Tcl issue parsing emojis that can cause a crash - Fixed an improper change to the display of bind flags that caused issues with Tcl scripts that parse bind flags - Added SSL header information to `.status` to help diagnose `./configure` mismatches - Lots of under-the-hood bug fixes ## Tcl API changes - Tcl minimum required version is now 8.5! This actually happened in version 1.9.0; upstream just forgot to tell people. Oops! :) ## Module changes - Updated `woobie.mod` with additional example code ## Documentation changes: - Added additional documentation to help write modules - Updated botnet docs to include reference to TLS docs for secure links - Updated Tcl repo from unmaintained FTP to HTTP repository ChangeLog: * Wed Mar 15 2023 Robert Scheck 1.9.5-1 - Upgrade to 1.9.5 (#2169600) * Thu Jan 19 2023 Fedora Release Engineering - 1.9.4-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2169600 - eggdrop-1.9.5 is available https://bugzilla.redhat.com/show_bug.cgi?id=2169600 lua-sec-1.3.0-1.el7 (FEDORA-EPEL-2023-2af38257a1) Lua binding for OpenSSL library Update Information: # LuaSec 1.3.0* Add `:getlocalchain()` and `:getlocalcertificate()` to mirror the peer methods * Add Pre-Shared Key (PSK) support ChangeLog: * Wed Mar 15 2023 Robert Scheck 1.3.0-1 - Upgrade to 1.3.0 (#2178605) * Thu Jan 19 2023 Fedora Release Engineering - 1.2.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2178605 - lua-sec-1.3.0 is available https://bugzilla.redhat.com/show_bug.cgi?id=2178605 rpminspect-data-centos-1.2-1.el7 (FEDORA-EPEL-2023-e2c396377a) Build deviation compliance tool data files for CentOS Update Information: Upgrade to rpminspect-data-centos-1.2 ChangeLog: * Tue Mar 14 2023 David Cantrell - 1.2-1 - Upgrade to rpminspect-data-centos-1.2 uglify-js-3.17.4-1.el7 (FEDORA-EPEL-2023-4ea2dd0cbb) JavaScript parser, mangler/compressor and beautifier toolkit Update Information: uglify-js 3.17.4 ChangeLog: * Wed Mar 15 2023 Mattias Ellert - 3.17.4-1 - Update to 3.17.4 - Rebuilt for updated rpm macros (Fedora 37+) * Sat Jan 21 2023 Fedora Release Engineering - 3.17.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild References: [ 1 ] Bug #2129629 - uglify-js-3.17.4 is available https://bugzilla.redhat.com/show_bug.cgi?id=2129629 ___ 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
