[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 201 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f9d6ff695a bibutils-6.6-1.el7 ghc-hs-bibutils-6.6.0.0-1.el7 pandoc-citeproc-0.3.0.1-4.el7 184 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 58 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6fa6cebc3 game-music-emu-0.6.2-1.el7 55 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b43fdd19c3 vcftools-0.1.16-1.el7 28 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-17b3c81533 cacti-1.2.0-1.el7 cacti-spine-1.2.0-2.el7 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bd6a1ae962 pdns-recursor-4.1.9-1.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-26a7022f9a golang-1.11.5-1.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-cf8b89de02 mosquitto-1.5.6-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5f60a8861f kf5-kauth-5.52.0-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing lynis-2.7.1-1.el7 pspg-1.6.3-3.el7 python-pykwalify-1.7.0-1.el7 znc-1.7.2-2.el7 Details about builds: lynis-2.7.1-1.el7 (FEDORA-EPEL-2019-31498466b9) Security and system auditing tool Update Information: 2.7.1 ChangeLog: * Thu Feb 14 2019 Gwyn Ciesla - 2.7.1-1 - 2.7.1 * Fri Feb 1 2019 Fedora Release Engineering - 2.7.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild References: [ 1 ] Bug #1671425 - lynis-2.7.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1671425 pspg-1.6.3-3.el7 (FEDORA-EPEL-2019-195b64fc72) A unix pager optimized for psql Update Information: A unix pager optimized for psql References: [ 1 ] Bug #1677259 - Review Request: pspg - A unix pager optimized for psql https://bugzilla.redhat.com/show_bug.cgi?id=1677259 python-pykwalify-1.7.0-1.el7 (FEDORA-EPEL-2019-7dae6fb5b6) Python lib/cli for JSON/YAML schema validation Update Information: Update to 1.7.0. Removed versions of BR References: [ 1 ] Bug #1384917 - Review Request: python-pykwalify - Python lib/cli for JSON/YAML schema validation https://bugzilla.redhat.com/show_bug.cgi?id=1384917 znc-1.7.2-2.el7 (FEDORA-EPEL-2019-3a504782e9) An advanced IRC bouncer Update Information: Don't use system crypto policy on epel7 ChangeLog: * Thu Feb 14 2019 Nick Bebout - 1.7.2-2 - Don't use system crypto policy on epel7 References: [ 1 ] Bug #1677366 - znc having cipher issues with Let's Encrypt certs https://bugzilla.redhat.com/show_bug.cgi?id=1677366 ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 62 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b7556983e8 tomcat-7.0.92-1.el6 58 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-a0ddb153b8 game-music-emu-0.6.2-1.el6 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-809dcc772f golang-1.11.5-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing lynis-2.7.1-1.el6 pspg-1.6.3-3.el6 Details about builds: lynis-2.7.1-1.el6 (FEDORA-EPEL-2019-736f88fe66) Security and system auditing tool Update Information: 2.7.1 ChangeLog: * Thu Feb 14 2019 Gwyn Ciesla - 2.7.1-1 - 2.7.1 * Fri Feb 1 2019 Fedora Release Engineering - 2.7.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild References: [ 1 ] Bug #1671425 - lynis-2.7.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1671425 pspg-1.6.3-3.el6 (FEDORA-EPEL-2019-2d7597445f) A unix pager optimized for psql Update Information: A unix pager optimized for psql References: [ 1 ] Bug #1677259 - Review Request: pspg - A unix pager optimized for psql https://bugzilla.redhat.com/show_bug.cgi?id=1677259 ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
On Thu, Feb 14, 2019 at 10:17:53AM -0600, Richard Shaw wrote: > Ok. I ran into an issue on EPEL 7 where I needed to update a package so it > could work with a package that was part of a Review Request. Then I found > out someone was using my library as part of validated software they were > developing. Lesson learned the hard way. Assuming this goes through I will > be able to update on point releases and they can chose whether to update > their whole system or not, in which case they would have to revalidate > anyway. This might be a case for offering the library as a module -- at least when we get the details around that worked out. -- Matthew Miller Fedora Project Leader ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
On Thu, Feb 14, 2019 at 10:24 AM Stephen John Smoogen wrote: > On Thu, 14 Feb 2019 at 11:19, Richard Shaw wrote: > > > > On Thu, Feb 14, 2019 at 10:14 AM Stephen John Smoogen > wrote: > >> > >> On Thu, 14 Feb 2019 at 09:34, Richard Shaw > wrote: > >> > > >> > Will this also allow more significant upgrades of EPEL packages > between minor releases? > >> > > >> > >> That is the purpose if the package maintainer and their consumers want > it. > > > > > > Ok. I ran into an issue on EPEL 7 where I needed to update a package so > it could work with a package that was part of a Review Request. Then I > found out someone was using my library as part of validated software they > were developing. Lesson learned the hard way. Assuming this goes through I > will be able to update on point releases and they can chose whether to > update their whole system or not, in which case they would have to > revalidate anyway. > > > > Correct, and they can also grab the old version out of archives and do > what they want versus dig through koji to find it. Then +1000 from me :) Thanks, Richard ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
On Thu, 14 Feb 2019 at 11:19, Richard Shaw wrote: > > On Thu, Feb 14, 2019 at 10:14 AM Stephen John Smoogen > wrote: >> >> On Thu, 14 Feb 2019 at 09:34, Richard Shaw wrote: >> > >> > Will this also allow more significant upgrades of EPEL packages between >> > minor releases? >> > >> >> That is the purpose if the package maintainer and their consumers want it. > > > Ok. I ran into an issue on EPEL 7 where I needed to update a package so it > could work with a package that was part of a Review Request. Then I found out > someone was using my library as part of validated software they were > developing. Lesson learned the hard way. Assuming this goes through I will be > able to update on point releases and they can chose whether to update their > whole system or not, in which case they would have to revalidate anyway. > Correct, and they can also grab the old version out of archives and do what they want versus dig through koji to find it. > Thanks, > Richard > ___ > 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://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org -- Stephen J Smoogen. ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
On Thu, 14 Feb 2019 at 09:34, Richard Shaw wrote: > > Will this also allow more significant upgrades of EPEL packages between minor > releases? > That is the purpose if the package maintainer and their consumers want it. > Thanks, > Richard > ___ > 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://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org -- Stephen J Smoogen. ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
On Thu, Feb 14, 2019 at 10:14 AM Stephen John Smoogen wrote: > On Thu, 14 Feb 2019 at 09:34, Richard Shaw wrote: > > > > Will this also allow more significant upgrades of EPEL packages between > minor releases? > > > > That is the purpose if the package maintainer and their consumers want it. > Ok. I ran into an issue on EPEL 7 where I needed to update a package so it could work with a package that was part of a Review Request. Then I found out someone was using my library as part of validated software they were developing. Lesson learned the hard way. Assuming this goes through I will be able to update on point releases and they can chose whether to update their whole system or not, in which case they would have to revalidate anyway. Thanks, Richard ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes
Will this also allow more significant upgrades of EPEL packages between minor releases? Thanks, Richard ___ 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://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
