Re: [EPEL-devel] Current update policy?
On Wed, Mar 18, 2015 at 10:39 AM, Kevin Fenzi wrote: > On Wed, 18 Mar 2015 08:00:35 -0700 > Dave Johansen wrote: > > > Is that really true? The Qt 5 package in EPEL 6 has been updated > > several times and I don't recall ever seeing an > > email/announcement/etc. > > Were the upgrades incompatible? You have to manually intervene? Honestly, on the machines I'm using, I installed 5.2 and haven't updated since 5.3 was released because I didn't want to rebuild and re-test all of my stuff, but my understanding of the following is that the upgrades are not completely compatible: http://upstream.rosalinux.ru/versions/qt.html ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] Current update policy?
On Wed, 18 Mar 2015 08:00:35 -0700 Dave Johansen wrote: > Is that really true? The Qt 5 package in EPEL 6 has been updated > several times and I don't recall ever seeing an > email/announcement/etc. Were the upgrades incompatible? You have to manually intervene? kevin pgp8riuWG8Exs.pgp Description: OpenPGP digital signature ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] Current update policy?
On Wed, Mar 18, 2015 at 6:34 AM, Kevin Fenzi wrote: > On Tue, 17 Mar 2015 21:36:41 -0700 > Dave Johansen wrote: > > > What is the current update policy for EPEL? The stated one seems to be > > along the lines of "no major changes" ( > > http://fedoraproject.org/wiki/Updates_Policy ) but it seems more like > > "whatever the packager is willing to maintain" is the actual policy. > > > > I ask because a bugzilla was just opened against a package I maintain > > ( https://bugzilla.redhat.com/show_bug.cgi?id=1201808 ) and I wanted > > to know how I should handle it. > > > > Does it need to be closed as wontfix? Or should a "notice of upcoming > > major update" policy be put in place to handle things like this? > > Rex already closed it as WONTFIX, however to expand on that: > > The current policy is to not change the user experence or require > manual intervention on updates if at all possible. There are some cases > where there's not much choice (like when the version shipped has > serious security or data loss bugs and a upgrade to a new version is > the only answer), but in those cases theres announcements to the > epel-announce list and lots of time in testing. > Is that really true? The Qt 5 package in EPEL 6 has been updated several times and I don't recall ever seeing an email/announcement/etc. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
[EPEL-devel] Fedora EPEL 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing: Age URL 1060 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5 514 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5 279 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1626/puppet-2.7.26-1.el5 133 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3784/mantis-1.2.17-3.el5 128 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3849/sblim-sfcb-1.3.8-2.el5 37 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0695/drupal7-path_breadcrumbs-3.2-1.el5 18 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1001/drupal7-entity-1.6-1.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1098/librsync-1.0.0-1.el5,duplicity-0.6.21-2.el5,rdiff-backup-1.0.5-3.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1121/dokuwiki-0-0.24.20140929c.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1044/putty-0.63-4.el5 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1029/phpMyAdmin4-4.0.10.9-1.el5 The following builds have been pushed to Fedora EPEL 5 updates-testing voms-2.0.12-3.el5 Details about builds: voms-2.0.12-3.el5 (FEDORA-EPEL-2015-1300) Virtual Organization Membership Service Update Information: VOMS clients (Java) 3.0.6. ChangeLog: * Wed Mar 18 2015 Mattias Ellert - 2.0.12-3 - Rename client package and make voms-clients a virtual provides ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 1060 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 125 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4008/cross-binutils-2.23.51.0.3-1.el6.1 113 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4242/facter-1.6.18-8.el6 101 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-4485/python-tornado-2.2.1-7.el6 63 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0232/chicken-4.9.0.1-2.el6 40 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0644/perl-Gtk2-1.2495-1.el6 37 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0696/drupal7-path_breadcrumbs-3.2-1.el6 30 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0779/drupal7-views-3.10-1.el6 19 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0864/nodejs-0.10.36-3.el6,libuv-0.10.34-1.el6,v8-3.14.5.10-17.el6 18 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0985/drupal7-entity-1.6-1.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1047/putty-0.63-4.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1107/dokuwiki-0-0.24.20140929c.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1108/librsync-1.0.0-1.el6,csync2-1.34-15.el6,duplicity-0.6.22-4.el6,rdiff-backup-1.2.8-6.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1173/seamonkey-2.28-4.ESR_31.5.0.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1177/libmspack-0.5-0.1.alpha.el6 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1069/phpMyAdmin-4.0.10.9-1.el6 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1286/nx-libs-3.5.0.29-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing httping-2.4-1.el6 mod_ruid2-0.9.8-2.el6 python-fedmsg-meta-fedora-infrastructure-0.4.5-1.el6 rednotebook-1.9.0-1.el6 uwsgi-2.0.9-3.el6 vdsm-4.16.12-0.el6 voms-2.0.12-3.el6 Details about builds: httping-2.4-1.el6 (FEDORA-EPEL-2015-1302) Ping alike tool for http requests Update Information: Update to new upstream release 2.4 ChangeLog: * Tue Mar 17 2015 Fabian Affolter - 2.4-1 - Update to new upstream release 2.4 mod_ruid2-0.9.8-2.el6 (FEDORA-EPEL-2015-1301) A suexec module for Apache Update Information: First release References: [ 1 ] Bug #1089561 - Review Request: mod_ruid2 - A suexec module for Apache https://bugzilla.redhat.com/show_bug.cgi?id=1089561 python-fedmsg-meta-fedora-infrastructure-0.4.5-1.el6 (FEDORA-EPEL-2015-1310) Metadata providers for Fedora Infrastructure's fedmsg deployment Update Information: New irc processors. ChangeLog: * Tue Mar 17 2015 Ralph Bean - 0.4.5-1 - new version * Mon Mar 16 2015 Ralph Bean - 0.4.4-1 - new version * Tue Feb 24 2015 Ralph Bean - 0.4.3-1 - new version * Tue Feb 24 2015 Ralph Bean - 0.4.2-1 - new version rednotebook-1.9.0-1.el6 (FEDORA-EPEL-2015-1306) A desktop diary Update Information: Update to new upstream version 1.9.0 ChangeLog: * Tue Mar 17 2015 Fabian Affolter - 1.9.0-1 - Update to new upstream version 1.9.0 * Fri Oct 17 2014 Christoph Wickert - 1.8.1-1 - Update to 1.8.1 * Sun Jun 8 2014 Fedora Release Engineering - 1.8.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Mon Jan 6 2014 Fabian Affolter - 1.8.0-1 - Update to new upstream version 1.8.0 * Sat Nov 16 2013 Fabian Affolter - 1.7.3-1 - Update to new upstream version 1.7.3 * Wed Jul 31 2013 Fabian Affolter - 1.7.2-1 - Update to new upstream version 1.7.2 * Sat Jun 8 2013 Fabian Affolter - 1.7.1-1 - Update to new upstream version 1.7.1 * Fri Mar 1 2013 Fabian Affolter - 1.7.0-1 - Upd
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 125 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3989/cross-binutils-2.23.88.0.1-2.el7.1 40 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0626/perl-Gtk2-1.2495-1.el7 19 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0862/nodejs-0.10.36-3.el7,libuv-0.10.34-1.el7,v8-3.14.5.10-17.el7 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1087/dokuwiki-0-0.24.20140929c.el7 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1135/librsync-1.0.0-1.el7,duplicity-0.6.24-5.el7,rdiff-backup-1.2.8-11.el7 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-0952/qpid-qmf-0.28-27.el7,qpid-cpp-0.30-12.el7 9 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1077/libmspack-0.5-0.1.alpha.el7 4 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1250/php-ZendFramework2-2.3.7-1.el7 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1278/nx-libs-3.5.0.29-1.el7 1 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1291/varnish-4.0.3-3.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing codec2-0.3-5.20150317svn2080.el7 httping-2.4-1.el7 libqalculate-0.9.7-7.el7 mod_ruid2-0.9.8-2.el7 python-fedmsg-meta-fedora-infrastructure-0.4.5-1.el7 qtwebkit-2.3.4-3.el7 rednotebook-1.9.0-1.el7 thunderbird-enigmail-1.8-1.el7 uwsgi-2.0.9-3.el7 voms-2.0.12-3.el7 voms-clients-java-3.0.6-1.el7 Details about builds: codec2-0.3-5.20150317svn2080.el7 (FEDORA-EPEL-2015-1311) Next-Generation Digital Voice for Two-Way Radio Update Information: Initial import (#1110386). References: [ 1 ] Bug #1110386 - Review Request: codec2 - Next-Generation Digital Voice for Two-Way Radio https://bugzilla.redhat.com/show_bug.cgi?id=1110386 httping-2.4-1.el7 (FEDORA-EPEL-2015-1305) Ping alike tool for http requests Update Information: Update to new upstream release 2.4 ChangeLog: * Tue Mar 17 2015 Fabian Affolter - 2.4-1 - Update to new upstream release 2.4 libqalculate-0.9.7-7.el7 (FEDORA-EPEL-2015-1297) Multi-purpose calculator library Update Information: Initial build for EPEL-7 mod_ruid2-0.9.8-2.el7 (FEDORA-EPEL-2015-1309) A suexec module for Apache Update Information: First release References: [ 1 ] Bug #1089561 - Review Request: mod_ruid2 - A suexec module for Apache https://bugzilla.redhat.com/show_bug.cgi?id=1089561 python-fedmsg-meta-fedora-infrastructure-0.4.5-1.el7 (FEDORA-EPEL-2015-1304) Metadata providers for Fedora Infrastructure's fedmsg deployment Update Information: New irc processors. Fixes to various processors. Notably, the koji long_form code got some fixes. New long-form implementations for lookaside, koji, and trac. Fixes to github, hotness, and elections messages. New longform output for github and irc meessages. Improved debug logging. Handle future bodhi2 messages. rpm.sign messages now indicate the key id. Handle new sigul messages. Bugfix for new pkgdb messages. Latest upstream. Handle a new message type from the-new-hotness. Change the way usernames are returned from pkgdb messages. ChangeLog: * Tue Mar 17 2015 Ralph Bean - 0.4.5-1 - new version * Mon Mar 16 2015 Ralph Bean - 0.4.4-1 - new version * Tue Feb 24 2015 Ralph Bean - 0.4.3-1 - new version * Tue Feb 24 2015 Ralph Bean - 0.4.2-1 - new version * Wed Feb 18 2015 Ralph Bean - 0.4.1-1 - new version * Tue Feb 10 2015 Ralph Bean - 0.4.0-1
Re: [EPEL-devel] Current update policy?
On Tue, 17 Mar 2015 21:36:41 -0700 Dave Johansen wrote: > What is the current update policy for EPEL? The stated one seems to be > along the lines of "no major changes" ( > http://fedoraproject.org/wiki/Updates_Policy ) but it seems more like > "whatever the packager is willing to maintain" is the actual policy. > > I ask because a bugzilla was just opened against a package I maintain > ( https://bugzilla.redhat.com/show_bug.cgi?id=1201808 ) and I wanted > to know how I should handle it. > > Does it need to be closed as wontfix? Or should a "notice of upcoming > major update" policy be put in place to handle things like this? Rex already closed it as WONTFIX, however to expand on that: The current policy is to not change the user experence or require manual intervention on updates if at all possible. There are some cases where there's not much choice (like when the version shipped has serious security or data loss bugs and a upgrade to a new version is the only answer), but in those cases theres announcements to the epel-announce list and lots of time in testing. kevin pgpZ9zXP98mPO.pgp Description: OpenPGP digital signature ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
