Re: EPEL Reformed Steering Committee
Howdy! Currently the ius-release package depends on epel-release. This is because several of our packages have dependencies from EPEL. Would these new proposed repos be supplementary to the current EPEL, or something else? Here are the current IUS mailing lists. Core developers: core...@iuscommunity.org ius-core...@lists.launchpad.net Community members: ius-commun...@lists.launchpad.net Carl George Rackspace GNU/Linux Engineer From: Rahul Sundaram [methe...@gmail.com] Sent: Friday, August 29, 2014 07:38 PM To: EPEL Development List Cc: core...@iuscommunity.org Subject: Re: EPEL Reformed Steering Committee Hi On Fri, Aug 29, 2014 at 5:12 PM, Stephen John Smoogen mailto:smo...@gmail.com>> wrote: On 29 August 2014 15:03, Rahul Sundaram mailto:methe...@gmail.com>> wrote: Hi On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items: 1) EPEL.next (EPIC or EPEL-rolling, etc) Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.] I am adding their contact email in CC Rahul ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reformed Steering Committee
Hi On Fri, Aug 29, 2014 at 5:12 PM, Stephen John Smoogen wrote: > > > > On 29 August 2014 15:03, Rahul Sundaram wrote: > >> Hi >> >> >> On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: >> >>> At last week's EPEL meeting, it was proposed that at least a short term >>> governing committee be put together to help on the following items: >>> >>> 1) EPEL.next (EPIC or EPEL-rolling, etc) >>> >> >> Has there been any attempt to bring in the people working on IUS >> repository? Perhaps their needs could be considered when launching new sub >> repositories >> >> > Not yet. It is a good idea to bring up at this point. Are there any IUS > people on the list already? Or do you know people we should contact? [The > IUS lists I am on are very very quiet so I am not sure who that would be > these days.] > I am adding their contact email in CC Rahul ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reformed Steering Committee
On 29 August 2014 16:15, Michael Stahnke wrote: > > > > On Fri, Aug 29, 2014 at 11:48 AM, Stephen John Smoogen > wrote: > >> At last week's EPEL meeting, it was proposed that at least a short term >> governing committee be put together to help on the following items: >> >> 1) EPEL.next (EPIC or EPEL-rolling, etc) >> 2) Formalizing various amounts of unwritten rules for package addition, >> removal and maintenance in current repos. >> 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been >> EPEL since the last EPSCO was around. >> > > Are EPEL.next and current EPEL going to be steered by the same people? > At the moment yes. > >> At that meeting the following people were nominated to the committee: >> >> Dennis Gilmore >> Kevin Fenzi >> Stephen Smoogen >> Jim Perrin >> >> Todays (2014-08-29) meeting this was 'formalized' with people attending >> the meeting. Added to that was a beginning proposal of committee >> governance: >> > > Is the meeting time also formalized? I can make this most of the time, but > forgot this morning. (Added to calendar now). > > Yes the meetings will be Friday 1600 UTC in #epel until changed. Any changes will be announced on this list. > >> The governance structure will be a short term organization to set up >> policies and procedues in place for continual maintenance of EPEL. The term >> of the committee will end 3 months after either new repos are setup or >> voted not going to happen by said committee. If a longer term running >> committee is required, the previous board will set up policies for >> elections and term lengths before the short term committee ends. >> >> After the meeting I realized that wasn't a good deadline so would like to >> alter it these changes should be completed by the Fedora 22 release date. >> > > When is this project release date? On > https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22 I see > 2015-XX-XX. That's a lot of leeway. > There is nothing more formal than that. I would expect that it will be 6 months after F21 which I am expecting to be in November/December of 2014 which would put 22 around June 2015. I think that getting all the items done by November/December is hard to meet but by June should be done. The committee can stand down at any time also. > > >> >> >> Working Motto: We put the SCO in Enterprise Linux >> > > Nice > >> >> > > ___ > epel-devel mailing list > epel-devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/epel-devel > > -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Help on some ruby package for /Fedora
I am primary point of contact on several ruby packages. Sadly, I haven't been able to give them the love and attention they need lately. I got into most of them when I had a different day job, and needed them in EPEL. Today I have less needs in that space. I'd love more co-maintainers, or even to orphan some of the following packages. Please sign up now for co-maintainerships. In a week or so I'll orphan the ones I have no interest in if nobody else picks up co-maintainership. ruby-dbus -- Ruby D-Bus client ( el6 el5 ) ruby-libvirt -- Ruby bindings for libvirt ( el6 el5 ) ruby-postgres -- A Ruby interface for the PostgreSQL database engine ( el6 el5 ) ruby-rpm -- Ruby bindings for RPM ( el6 el5 ) ruby-sqlite3 -- A Ruby interface for the SQLite database engine ( el6 el5 ) rubygem-ParseTree -- Extracts the parse tree for a class/method and returns an s-expression ( el6 el5 ) rubygem-RedCloth -- Textile parser for Ruby ( master f21 f20 f19 el6 el5 ) rubygem-RubyInline -- Write foreign code within your ruby code ( el6 el5 ) rubygem-ZenTest -- Automated test scaffolding for Ruby ( el6 el5 ) rubygem-abstract -- Allows you to define an abstract method in Ruby ( el6 el5 ) rubygem-actionmailer -- Service layer for easy email delivery and testing ( el6 el5 ) rubygem-actionpack -- Web-flow and rendering framework putting the VC in MVC ( el6 el5 ) rubygem-actionwebservice -- Web service support for Action Pack ( el6 el5 ) rubygem-activeldap -- Ruby/ActiveLdap is a object-oriented API to LDAP ( el6 ) rubygem-activerecord -- Implements the ActiveRecord pattern for ORM ( el6 el5 ) rubygem-activeresource -- Active Record for web resources ( el6 el5 ) rubygem-activesupport -- Support and utility classes used by the Rails framework ( el6 el5 ) rubygem-amqp -- AMQP client implementation in Ruby/EventMachine ( el6 el5 ) rubygem-archive-tar-minitar -- Provides POSIX tar archive management from Ruby programs ( el6 el5 ) rubygem-bunny -- Another synchronous Ruby AMQP client ( el6 el5 ) rubygem-configuration -- Pure Ruby scoped configuration files ( master f21 f20 f19 ) rubygem-crack -- Really simple JSON and XML parsing, ripped from Merb and Rails ( master f21 f20 f19 el6 el5 ) rubygem-erubis -- A fast and extensible eRuby implementation ( el6 el5 ) rubygem-eventmachine -- Ruby/EventMachine library ( el6 el5 ) rubygem-extlib -- Support library for DataMapper and Merb ( el6 el5 ) rubygem-facon -- Tiny mocking library ( master f21 f20 f19 el6 el5 ) rubygem-fakeweb -- A tool for faking responses to HTTP ( master f21 f20 f19 el6 el5 ) rubygem-flexmock -- Mock object library for ruby ( el5 ) rubygem-gettext -- RubyGem of Localization Library and Tools for Ruby ( el6 el5 ) rubygem-gettext_activerecord -- Localization support for ActiveRecord by Ruby-GetText-Package ( el6 el5 ) rubygem-haml -- XHTML/XML templating engine ( el6 el5 ) rubygem-httparty -- Makes HTTP fun! Also, makes consuming restful web services dead easy ( master f21 f20 f19 el6 el5 ) rubygem-jnunemaker-matchy -- RSpec-esque matchers for use in Test::Unit ( master f21 f20 f19 el6 el5 ) rubygem-launchy -- Helper class for cross-platform launching of applications ( master f21 f20 f19 ) rubygem-locale -- Pure ruby library which provides basic APIs for localization ( el6 el5 ) rubygem-mime-types -- Return the MIME Content-Type for a given filename ( el6 el5 ) rubygem-mixlib-authentication -- Simple per-request authentication ( el6 el5 ) rubygem-mixlib-cli -- Simple ruby mixin for CLI interfaces ( el6 el5 ) rubygem-mixlib-config -- Simple ruby config mixin ( el6 el5 ) rubygem-mixlib-log -- Ruby mixin for log functionality ( el6 el5 ) rubygem-moneta -- A unified interface to key/value stores ( el6 el5 ) rubygem-newgem -- Bundle Ruby libraries into a RubyGem ( el6 el5 ) rubygem-pkg-config -- A pkg-config implmenetation by Ruby ( el6 el5 ) rubygem-rails -- Web-application framework ( el6 el5 ) rubygem-rcov -- Code coverage analysis tool for Ruby ( el6 el5 ) rubygem-rspec -- Behaviour driven development (BDD) framework for Ruby ( master f21 f20 f19 epel7 el6 el5 ) rubygem-rubigen -- A framework to allow Ruby applications to generate file/folder stubs ( master f21 f20 f19 ) rubygem-ruby-ole -- Ruby OLE library ( master f21 f20 f19 el6 el5 ) rubygem-ruby2ruby -- Generate pure ruby from RubyParser compatible Sexps ( el6 el5 ) rubygem-ruby_parser -- A ruby parser written in pure ruby ( el6 el5 ) rubygem-rubyforge -- A script which automates a limited set of rubyforge operations ( el6 ) rubygem-sexp_processor -- A branch of ParseTree providing generic sexp processing tools ( el6 el5 ) rubygem-simple-rss -- A simple, flexible, extensible, and liberal RSS and Atom reader for Ruby ( master f21 f20 f19 el6 el5 ) rubygem-systemu -- Multi-platform command execution and capture ( epel7 el6 el5 ) rubygem-templater -- Ruby framework for building code generators ( el6 el5 ) rubygem-test-spec -- Behaviour Driven Development interface for Test::Unit ( master f21 f20 f19 ) rubygem-thor -- Scrip
Re: EPEL Reformed Steering Committee
On Fri, Aug 29, 2014 at 11:48 AM, Stephen John Smoogen wrote: > At last week's EPEL meeting, it was proposed that at least a short term > governing committee be put together to help on the following items: > > 1) EPEL.next (EPIC or EPEL-rolling, etc) > 2) Formalizing various amounts of unwritten rules for package addition, > removal and maintenance in current repos. > 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been EPEL > since the last EPSCO was around. > Are EPEL.next and current EPEL going to be steered by the same people? > > At that meeting the following people were nominated to the committee: > > Dennis Gilmore > Kevin Fenzi > Stephen Smoogen > Jim Perrin > > Todays (2014-08-29) meeting this was 'formalized' with people attending > the meeting. Added to that was a beginning proposal of committee > governance: > Is the meeting time also formalized? I can make this most of the time, but forgot this morning. (Added to calendar now). > > The governance structure will be a short term organization to set up > policies and procedues in place for continual maintenance of EPEL. The term > of the committee will end 3 months after either new repos are setup or > voted not going to happen by said committee. If a longer term running > committee is required, the previous board will set up policies for > elections and term lengths before the short term committee ends. > > After the meeting I realized that wasn't a good deadline so would like to > alter it these changes should be completed by the Fedora 22 release date. > When is this project release date? On https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22 I see 2015-XX-XX. That's a lot of leeway. > > > Working Motto: We put the SCO in Enterprise Linux > Nice > > ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL EpSCO Email Meeting:
So in todays (2014-08-29) meeting, we wanted to move the various policy discussions to email so that people could take their time to reply and also to allow for people who could not attend time to respond. Going from the web-page https://fedoraproject.org/wiki/EPEL-faster-repo-ideas the following items are listed (with additions I added while writing this email.) I would like to start with the EpSCO governance to just get that out of the way and then move to current rules as we see them. I can act as secretary to make sure that changes discussed here are put in place on the wiki or other places. Policy questions - EpSCO governance. - Lifetime of initial committee (9 months?) - Replacement of any exiting members (replacement by formal vote, etc). - Size of committee (4 members? 5 members?) - Meeting rules (follow https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee ) - How many repos? (examples below) - epel, - epel-test - epel-rolling - epel-rolling-test ? - epel-edge ? - epel-edge-test ? - What would faster moving mean? - Would packages in this be able to conflict with epel packages? Base packages? - When would incompatible changes be allowed in each branch? - Different guidelines for specs/packages per branch? - When would a package be expired or removed? - What are the rules for EPEL packages currently? - Currently packages require of 2 weeks in EPEL-testing before promotion to EPEL. - Can this be changed to 1 week? - What Constant Integration would be needed to give auto-karma? - How to integrate packages shepherded by CentOS (or other SIGS) which may conflict with EPEL packages? -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reformed Steering Committee
On 29 August 2014 15:03, Rahul Sundaram wrote: > Hi > > > On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: > >> At last week's EPEL meeting, it was proposed that at least a short term >> governing committee be put together to help on the following items: >> >> 1) EPEL.next (EPIC or EPEL-rolling, etc) >> > > Has there been any attempt to bring in the people working on IUS > repository? Perhaps their needs could be considered when launching new sub > repositories > > Not yet. It is a good idea to bring up at this point. Are there any IUS people on the list already? Or do you know people we should contact? [The IUS lists I am on are very very quiet so I am not sure who that would be these days.] -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reformed Steering Committee
Hi On Fri, Aug 29, 2014 at 2:48 PM, Stephen John Smoogen wrote: > At last week's EPEL meeting, it was proposed that at least a short term > governing committee be put together to help on the following items: > > 1) EPEL.next (EPIC or EPEL-rolling, etc) > Has there been any attempt to bring in the people working on IUS repository? Perhaps their needs could be considered when launching new sub repositories Rahul ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Fedora 5 updates-testing report
The following Fedora EPEL 5 Security updates need testing:
Age URL
859
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5
314
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11893/libguestfs-1.20.12-1.el5
78
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1626/puppet-2.7.26-1.el5
69
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1696/perl-Email-Address-1.905-1.el5
63
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1747/mediawiki119-1.19.17-1.el5
21
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2153/drupal6-6.33-1.el5
21
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2150/drupal7-7.31-1.el5
16
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2184/389-ds-base-1.2.11.30-1.el5
0
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2269/GraphicsMagick-1.3.20-3.el5
0
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2300/zarafa-7.1.10-4.el5
0
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2304/xine-lib-1.1.21-10.el5
0
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2308/python-elixir-0.5.0-2.el5
The following builds have been pushed to Fedora EPEL 5 updates-testing
GraphicsMagick-1.3.20-3.el5
cabal-rpm-0.9.1-1.el5
cmake-fedora-2.3.0-1.el5
openblas-0.2.11-1.el5
perl-YAML-0.66-3.el5
python-elixir-0.5.0-2.el5
xine-lib-1.1.21-10.el5
zarafa-7.1.10-4.el5
Details about builds:
GraphicsMagick-1.3.20-3.el5 (FEDORA-EPEL-2014-2269)
An ImageMagick fork, offering faster image generation and better quality
Update Information:
New stable upstream release, patched for CVE-2014-1947. See also:
http://www.graphicsmagick.org/NEWS.html#august-16-2014
ChangeLog:
* Thu Aug 28 2014 Rex Dieter 1.3.20-3
- go back to original L%02d format variant
* Mon Aug 25 2014 Rex Dieter 1.3.20-2
- better fix for CVE-2014-1947 (#1064098,#1083082)
* Wed Aug 20 2014 Rex Dieter 1.3.20-1
- 1.3.20, CVE-2014-1947 (#1064098,#1083082)
* Fri Aug 15 2014 Fedora Release Engineering
- 1.3.19-9
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
* Wed Aug 13 2014 Orion Poplawski - 1.3.19-8
- Rebuild for libjbig soname bump
* Fri Jun 6 2014 Fedora Release Engineering
- 1.3.19-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
* Sun May 11 2014 Rex Dieter 1.3.19-6
- handle upgrade path for introduction of -doc subpkg in 1.3.19-4
* Mon Feb 3 2014 Remi Collet - 1.3.19-5
- upstream patch, drop debug output (#1060665)
* Sat Jan 25 2014 Ville Skyttä - 1.3.19-4
- Split docs into -doc subpackage, drop README.txt (#1056306).
- Drop no longer needed BrowseDelegateDefault modification.
- Convert docs to UTF-8.
* Thu Jan 9 2014 Rex Dieter 1.3.19-3
- ppc64le is a multilib arch (#1051208)
* Wed Jan 1 2014 Rex Dieter 1.3.19-2
- BR: jbigkit, libwebp, xdg-utils, xz
* Wed Jan 1 2014 Rex Dieter 1.3.19-1
- 1.3.19 (#1047676)
* Tue Oct 15 2013 Rex Dieter 1.3.18-5
- trim changelog
* Fri Aug 2 2013 Fedora Release Engineering
- 1.3.18-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
* Wed Jul 17 2013 Petr Pisar - 1.3.18-3
- Perl 5.18 rebuild
References:
[ 1 ] Bug #1064098 - CVE-2014-1947 ImageMagick: PSD writing layer name buffer
overflow ("L%02ld")
https://bugzilla.redhat.com/show_bug.cgi?id=1064098
cabal-rpm-0.9.1-1.el5 (FEDORA-EPEL-2014-2295)
RPM packaging tool for Haskell Cabal-based packages
Update Information:
Haskell cabal packaging tool
Latest version:
- supports packaging on RHEL5 and SUSE
- uses existing spec file and preps correct source version
- 'install' command supports local recursive rpmbuilding
- recursive 'missingdeps'
References:
[ 1 ] Bug #855701 - Review Request: cabal-rpm - creates rpm spec files for
Haskell Cabal packages
https://bugzilla.redhat.com/show_bug.cgi?id=855701
cmake-fedora-2.3.0-1.el5 (FEDORA-EPEL-2014-2305)
CMake helper modules for fedora developers
Update Information:
- cmake-fedora-fedpkg: fix try_command
- ManageChangeLogScript: New comman
EPEL Fedora 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 859 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6 191 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0590/oath-toolkit-2.0.2-4.el6 78 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1616/puppet-2.7.26-1.el6 69 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1693/perl-Email-Address-1.905-1.el6 28 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2099/v8-3.14.5.10-11.el6 21 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2148/drupal6-6.33-1.el6 14 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2218/pen-0.25.1-1.el6 11 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2229/phpMyAdmin-4.0.10.2-1.el6 8 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2255/distcc-3.2rc1-2.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2310/Django14-1.4.14-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2299/libmodplug-0.8.8.5-1.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2257/GraphicsMagick-1.3.20-3.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2307/zarafa-7.1.10-4.el6 0 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2302/xine-lib-1.1.21-10.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing Django14-1.4.14-1.el6 GraphicsMagick-1.3.20-3.el6 MUMPS-4.10.0-20.el6 cabal-rpm-0.9.1-1.el6 cmake-fedora-2.3.0-1.el6 fedfs-utils-0.9.7-1.el6 fedmsg-0.10.0-1.el6 fetch-crl-3.0.14-1.el6 inxi-2.2.1-1.el6 libmodplug-0.8.8.5-1.el6 openblas-0.2.11-1.el6 opendnssec-1.4.6-1.el6 pgp-tools-1.1.5-4.el6 python-docker-registry-core-2.0.1-1.el6 xine-lib-1.1.21-10.el6 zarafa-7.1.10-4.el6 Details about builds: Django14-1.4.14-1.el6 (FEDORA-EPEL-2014-2310) A high-level Python Web framework Update Information: Security fix for CVE-2014-0480, CVE-2014-0481, CVE-2014-0482, CVE-2014-0483 ChangeLog: * Wed Aug 27 2014 Matthias Runge - 1.4.14-1 - update to 1.4.14 fixing various flaws (rhbz#1132776) References: [ 1 ] Bug #1129950 - CVE-2014-0480 Django: reverse() can generate URLs pointing to other hosts, leading to phishing attacks https://bugzilla.redhat.com/show_bug.cgi?id=1129950 [ 2 ] Bug #1129952 - CVE-2014-0481 Django: file upload denial of service https://bugzilla.redhat.com/show_bug.cgi?id=1129952 [ 3 ] Bug #1129954 - CVE-2014-0482 Django: RemoteUserMiddleware session hijacking https://bugzilla.redhat.com/show_bug.cgi?id=1129954 [ 4 ] Bug #1129959 - CVE-2014-0483 Django: data leakage via querystring manipulation in admin https://bugzilla.redhat.com/show_bug.cgi?id=1129959 GraphicsMagick-1.3.20-3.el6 (FEDORA-EPEL-2014-2257) An ImageMagick fork, offering faster image generation and better quality Update Information: New stable upstream release, patched for CVE-2014-1947. See also: http://www.graphicsmagick.org/NEWS.html#august-16-2014 ChangeLog: * Thu Aug 28 2014 Rex Dieter 1.3.20-3 - go back to original L%02d format variant * Mon Aug 25 2014 Rex Dieter 1.3.20-2 - better fix for CVE-2014-1947 (#1064098,#1083082) * Wed Aug 20 2014 Rex Dieter 1.3.20-1 - 1.3.20, CVE-2014-1947 (#1064098,#1083082) * Fri Aug 15 2014 Fedora Release Engineering - 1.3.19-9 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild * Wed Aug 13 2014 Orion Poplawski - 1.3.19-8 - Rebuild for libjbig soname bump * Fri Jun 6 2014 Fedora Release Engineering - 1.3.19-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Sun May 11 2014 Rex Dieter 1.3.19-6 - handle upgrade path for introduction of -doc subpkg in 1.3.19-4 * Mon Feb 3 2014 Remi Collet - 1.3.19-5 - upstream patch, drop debug output (#1060665) * Sat Jan 25 2014 Ville Skyttä - 1.3.19-4 - Split docs into -doc subpackage, drop README.txt (#1056306). - Drop no longer needed BrowseDelegateDefault modification. - Convert docs to UTF-8. * Thu Jan 9 2014 Rex Dieter 1.3.19-3 - ppc64le is a multilib arch (#1051208) * Wed Jan 1 2014 Rex Dieter 1.3.19-2 - BR: jbigkit, libwebp, xdg-utils, xz * Wed Jan 1 2014 Rex Dieter 1.3.19-1 - 1.3.19 (#1047676) * Tue Oct 15 2013 Rex Dieter 1.3.18-5 - trim changelog -
EPEL Reformed Steering Committee
At last week's EPEL meeting, it was proposed that at least a short term governing committee be put together to help on the following items: 1) EPEL.next (EPIC or EPEL-rolling, etc) 2) Formalizing various amounts of unwritten rules for package addition, removal and maintenance in current repos. 3) Lower workload on Kevin Fenzi and Dennis Gilmore as they have been EPEL since the last EPSCO was around. At that meeting the following people were nominated to the committee: Dennis Gilmore Kevin Fenzi Stephen Smoogen Jim Perrin Todays (2014-08-29) meeting this was 'formalized' with people attending the meeting. Added to that was a beginning proposal of committee governance: The governance structure will be a short term organization to set up policies and procedues in place for continual maintenance of EPEL. The term of the committee will end 3 months after either new repos are setup or voted not going to happen by said committee. If a longer term running committee is required, the previous board will set up policies for elections and term lengths before the short term committee ends. After the meeting I realized that wasn't a good deadline so would like to alter it these changes should be completed by the Fedora 22 release date. Working Motto: We put the SCO in Enterprise Linux -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL Summary of Meeting 2014-08-29
#epel: EPEL (2014-08-29) Meeting started by smooge at 16:00:13 UTC. The full logs are available athttp://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-08-29-16.00.log.html . Meeting summary --- * meet and greets (smooge, 16:01:04) * meet and greets (smooge, 16:01:31) * Agenda (smooge, 16:04:22) * 1) Meet and Greets (smooge, 16:04:38) * 2) Agenda (smooge, 16:04:45) * 3) EPEL 7 out of beta (smooge, 16:04:54) * 4) EPEL. discussion (smooge, 16:05:06) * 5) Open Flood (smooge, 16:05:17) * 6) End meeting (smooge, 16:05:24) * EPEL 7 out of beta (smooge, 16:05:37) * Bodhi needs to get some work done still (smooge, 16:07:20) * updates do not work correctly yet but will soon. (smooge, 16:07:31) * EPEL. discussion (smooge, 16:17:22) * ACTION: Jeff_S and dgilmore and others to discuss .rpmsave issue (smooge, 16:20:11) * AGREED: EPEL short term governance team members: smooge, nirik, dgilmore, and Evolution (smooge, 16:29:35) * moving discussion of governance structure and policy to mailing list. Votes to finalize anything that feels need a vote will be next weeks meeting (smooge, 16:49:13) * Open Flood. (smooge, 16:49:47) * ACTION: Add time in testing to policy discussion on mailing list (smooge, 16:57:59) * Thanks for coming everyone. See you on the list. (smooge, 17:13:57) Meeting ended at 17:14:12 UTC. Action Items * Jeff_S and dgilmore and others to discuss .rpmsave issue * Add time in testing to policy discussion on mailing list Action Items, by person --- * dgilmore * Jeff_S and dgilmore and others to discuss .rpmsave issue * Jeff_S * Jeff_S and dgilmore and others to discuss .rpmsave issue * **UNASSIGNED** * Add time in testing to policy discussion on mailing list People Present (lines said) --- * smooge (97) * Jeff_S (43) * dgilmore (42) * nirik (33) * kbsingh (31) * maxamillion (26) * avij (8) * bstinson (6) * zodbot (3) * orionp (2) * Ussat (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Minutes: http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-08-29-16.00.html Minutes (text): http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-08-29-16.00.txt Log: http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-08-29-16.00.log.html -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reminder: 2014-08-29 meeting #epel
On Fri, Aug 29, 2014 at 1:49 AM, Karanbir Singh wrote: > On 08/28/2014 11:11 PM, Stephen John Smoogen wrote: > > > > We will be holding our weekly EPEL meeting tomorrow at 1600 UTC. > > > > Topics will be: > > > > 1) EPEL-7 moves out of Beta > > 2) EPEL. > > 3) Open Flood. > > I have another meeting that runs to 16:30, will drop in right after and > would really like to talk about politices and process around overlapping > content in not-distro CentOS repos and EPEL. > > I'll be there assuming the latest Freenode DoS settles down by then (I can't send to any channels at the moment). One more topic for the list -- I'd like to discuss the testing/stable policy (https://fedoraproject.org/wiki/EPEL_Updates_Policy). Specifically, I'd like to see the requirement lowered from two weeks because I don't actually think much testing happens in that time, so it just ends up being a barrier for contributors. I'd like to see the testing time requirement lowered/dropped globally, or at least a way for "trusted" packagers to bypass it without going through a per-update approval process. Thanks Smooge for pulling these together and for sending out the reminder. -Jeff ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL moving epel 7 out of beta
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 29 Aug 2014 07:53:06 +0200 Remi Collet wrote: > Le 28/08/2014 23:26, Dennis Gilmore a écrit : > > Hi All, > > > > Kevin and I working to move epel 7 out of beta, as of a few hours > > ago builds require bodhi updates to get pushed out. > > EPEL-7 is now on Bodhi. > > But trying to push an update for a freshly buld package: > > "No package found on these branches: el7" > > Any idea ? Bodi has hard coded assumptions about epel and wasn't updated to deal with the changes we made for epel7 it will be fixed today. Dennis > Remi. > > > P.S.: > Package: php-horde-Horde-Mime-2.4.5-1.el7 > Tag: epel7-testing-candidate > Status: complete > ___ > epel-devel mailing list > epel-devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/epel-devel -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUAHCAAAoJEH7ltONmPFDRAJ0QANMyzMXn4ASbBw7gyGQevZam tZpBUc6Nb+3tIj32cBWaC5GOOuVMeheLMWcnukCYBa63a38Z0uBk58lYfzEWh8s0 GHiKpjjp5uQSB6k8ksVQ7SFdPkAP4m9Iqg/5/CEFoj+eVFpD0EmFIVH646Zf4CmJ u61eY1YnCKqNkaCalQro+sNTnzxli0hwfKruTIEssOqqkLHAbH+puYWB2MPXQmUw IHh9qESQnzcB+KgOHnjy6J6LeXu1Jv3uDmwZ+no7tkA3n43ECIAFlgH8OMmdH3Id +WV/JQWk/LfIV7YuC5RcevYwZSbL8YKhT8Oy8DMaD81LbrLbgvnigVHlhzRq/Lk+ xZYheoz5tn5m5U0BosvoNY26HJ/KV0hBdYyk8SrISr/D9JnyX+dC6keQ23Mh/ecP ZQejcaQZH6jnmMWeTwAOcVCWFqcX9BRLYL8dhApg8icAc8arGHQYtGoUipVytDIi am7u+M4VfQBAAtsmpe+bbGaCPih5B9gjY6RK11ClIIObMjKn41gropmKbdNWPv+O sGjBXw9TpBzvnx2rkRLMzFUOKVrE3y4L0UHhk5scIEAYfpkZNUD0/KI9MpmLGqGS yzNpjLd3BGYD/pV54ewQj/NCvv+kVZ6iAzhYjqTXtEY8QJTVeVb/HcFLvsSI6GQE uG0AbZ5TPuDR1gRGBeu+ =ju0W -END PGP SIGNATURE- ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: EPEL Reminder: 2014-08-29 meeting #epel
On 08/28/2014 11:11 PM, Stephen John Smoogen wrote: > > We will be holding our weekly EPEL meeting tomorrow at 1600 UTC. > > Topics will be: > > 1) EPEL-7 moves out of Beta > 2) EPEL. > 3) Open Flood. I have another meeting that runs to 16:30, will drop in right after and would really like to talk about politices and process around overlapping content in not-distro CentOS repos and EPEL. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EPEL EPIC minor release branches
Hi, I read the log from last weeks EPEL meeting [1]. It is great to see discuss happening on (codename:) EPIC. :-) At Flock at the EPEL.next session there was mention of using branches/tags per minor EL version for EPIC for greater long term flexibility, which I thought sounded pretty attractive: it would allow people to switch to a newer version of EPIC when they are ready rather either being stuck on EPEL or forced to upgrade to the latest greatest immediately. Granted there are questions around how (long) to maintain the older release branches, but I think this can be handled by EOL policy similar to what we have for Fedora. I think having EPIC not just be a rolling release would be a big advantage over EPEL and it would fit with the release model that is already working well for RHEL/Centos et al. I feel EPEL/EPIC is too long lived not to have branches. :) I would have liked to have join the meeting tonight to discuss but it is at 1am in my timezone unfortunately... Jens [1] http://meetbot.fedoraproject.org/epel/2014-08-22/epel_reboot.2014-08-22-16.00.html ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
