[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Dave Johansen
On Thu, Aug 25, 2016 at 2:34 PM, Kevin Fenzi wrote: > On Wed, 24 Aug 2016 21:59:55 -0600 > Dave Johansen wrote: > > > I agree that how to handle SCLs can get really mess really fast, but > > a lot of projects are jumping on the "modern C++" bandwagon and

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Kevin Fenzi
On Thu, 25 Aug 2016 12:52:46 -0400 Stephen John Smoogen wrote: > On 25 August 2016 at 02:14, dani wrote: > > When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( > >

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Kevin Fenzi
On Wed, 24 Aug 2016 21:59:55 -0600 Dave Johansen wrote: > I agree that how to handle SCLs can get really mess really fast, but > a lot of projects are jumping on the "modern C++" bandwagon and > allows devtoolset is low risk, easy to do and enables a lot of > packages to

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 25 August 2016 at 12:49, Stephen John Smoogen wrote: > On 24 August 2016 at 23:59, Dave Johansen wrote: >> On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: >> >> I agree that how to handle SCLs can get really mess really fast,

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 25 August 2016 at 02:14, dani wrote: > When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/F5JXEYPKQY77NRBCL4MNUBS3K2YYBBTU/ > ) the response was an unequivocal no, EPEL does

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread Stephen John Smoogen
On 24 August 2016 at 23:59, Dave Johansen wrote: > On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: >> >> On Wed, 24 Aug 2016 16:43:31 -0600 >> Dave Johansen wrote: >> >> > On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi

[EPEL-devel] Re: nodejs update

2016-08-25 Thread Rich Megginson
On 08/11/2016 05:43 AM, Stephen Gallagher wrote: On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: Hi! As some of you may know, nodejs package that is present in EPEL is pretty outdated. The current v0.10 that we have will go EOL in October and npm (package manager) is already not maintained.

[EPEL-devel] Re: nodejs update

2016-08-25 Thread Matthias Runge
On 23/08/16 03:48, Stephen Gallagher wrote: >> On Mon, Aug 22, 2016 at 4:23 PM, Stephen Gallagher >> > >> Let me (or open a rel-eng ticket) when you want a epel7-nodejs6 side >> tag to build it into. Will make it easier so you don't need to deal >> with a billion

[EPEL-devel] Re: python34 for EPEL6

2016-08-25 Thread Tomas Orsava
On 08/24/2016 11:39 PM, Neal Gompa wrote: On Wed, Aug 24, 2016 at 5:38 PM, Orion Poplawski wrote: I have no idea if there is any interest in this or not. I managed to get the EPEL7 python34 package to build on EL6 with a few modifications. Is there any interest in

[EPEL-devel] Re: python34 for EPEL6

2016-08-25 Thread Avram Lubkin
On Wed, Aug 24, 2016 at 8:44 PM, Jason L Tibbitts III wrote: > > To be completely fair, I don't actually know EPEL policy here. The rule > is that you can't conflict with RHEL packages, but SRPMs aren't really > installed the same way as other packages and whether or not they

[EPEL-devel] Re: python34 for EPEL6

2016-08-25 Thread Avram Lubkin
> > Which is an annoying bit of process, but it would be quite possible to > exempt those packages from needing package reviews. It needn't take > that long. > > Not needing reviews would help, but I wonder how hard it would be to make them children of python-PACKAGE. The main issue is the SRPM

[EPEL-devel] Re: python34 for EPEL6

2016-08-25 Thread Avram Lubkin
Definitely, but it runs into the same problem as 3.4 on EL7, the fact that there are few packages available and adding them when the package already exists in RHEL requires creating a separate parent package in Fedora pkgdb. On Wed, Aug 24, 2016 at 5:38 PM, Orion Poplawski

[EPEL-devel] Fedora EPEL 7 updates-testing report

2016-08-25 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 535 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 297 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 60

[EPEL-devel] Re: python34 for EPEL6

2016-08-25 Thread Antonio Trande
On 08/24/2016 11:38 PM, Orion Poplawski wrote: > I have no idea if there is any interest in this or not. I managed to get the > EPEL7 python34 package to build on EL6 with a few modifications. Is there any > interest in supporting this? > > > > ___

[EPEL-devel] Fedora EPEL 5 updates-testing report

2016-08-25 Thread updates
The following Fedora EPEL 5 Security updates need testing: Age URL 805 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626 puppet-2.7.26-1.el5 654 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849 sblim-sfcb-1.3.8-2.el5 297

[EPEL-devel] Fedora EPEL 6 updates-testing report

2016-08-25 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 413 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 407 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 339

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

2016-08-25 Thread dani
When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/F5JXEYPKQY77NRBCL4MNUBS3K2YYBBTU/ ) the response was an unequivocal no, EPEL does not install to /opt/ , so it dies right there. Now you are