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 wrote:
> >
> > > On Tue, 23 Aug 2016 14:21:24 +0100
> > > Karanbir Singh
> "AL" == Avram Lubkin writes:
AL> I'm curious if anyone else has any insight. Maybe it is worth
AL> bringing up at a FPC meeting.
That would more appropriately be a topic of an EPEL meeting, since this
is purely an EPEL policy issue.
- J<
> "AL" == Avram Lubkin writes:
AL> Not needing reviews would help, but I wonder how hard it would be to
AL> make them children of python-PACKAGE. The main issue is the SRPM
AL> needs to have a different name so there is no conflict with the RHEL
AL> SRPM.
To be
On Wed, 24 Aug 2016 16:43:31 -0600
Dave Johansen wrote:
> On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi wrote:
>
> > On Tue, 23 Aug 2016 14:21:24 +0100
> > Karanbir Singh wrote:
> >
> > > On 22/08/16 18:30, Jason L Tibbitts III
On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi wrote:
> On Tue, 23 Aug 2016 14:21:24 +0100
> Karanbir Singh wrote:
>
> > On 22/08/16 18:30, Jason L Tibbitts III wrote:
> > >> "DJ" == Dave Johansen writes:
> > >
> > > DJ>
On 08/24/2016 04:58 PM, Dave Johansen wrote:
On Wed, Aug 24, 2016 at 3: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
> "AL" == Avram Lubkin writes:
AL> Definitely, but it runs into the same problem as 3.4 on EL7, the
AL> fact that there are few packages available and adding them when the
AL> package already exists in RHEL requires creating a separate parent
AL> package in Fedora
On Tue, 23 Aug 2016 14:21:24 +0100
Karanbir Singh wrote:
> On 22/08/16 18:30, Jason L Tibbitts III wrote:
> >> "DJ" == Dave Johansen writes:
> >
> > DJ> devtoolset is designed to do all of this and is already done,
> > DJ> so it seems that
On Wed, Aug 24, 2016 at 3: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?
>
How about using the
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 supporting this?
>
I think the Koji people
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?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office
The following Fedora EPEL 7 Security updates need testing:
Age URL
534 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
59
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
338
On Wed, 24 Aug 2016 13:47:41 +0200
Nikos Mavrogiannopoulos wrote:
> Hi,
> I'm reviewing package [0] for inclusion into epel6 but it provides a
> devel package which conflicts with an other devel package from rhel.
> In https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
Hi,
I'm reviewing package [0] for inclusion into epel6 but it provides a
devel package which conflicts with an other devel package from rhel. In
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies it says "EPEL
packages must never conflict with packages in RHEL Base", however, I'm
not sure
15 matches
Mail list logo