Re: EPEL Python 3 for 7?

On Fri, Jan 17, 2014 at 10:55:09AM -0500, Matthew Miller wrote: On Fri, Jan 17, 2014 at 08:05:23AM -0700, Dave Johansen wrote: system.so we've mostly decided that things in the system shouldn't use SCLs to work. So we still need to solve the problem of newer python interpreter

Re: EPEL Python 3 for 7?

On Fri, Jan 17, 2014 at 01:57:18PM -0500, Matthew Miller wrote: On Fri, Jan 17, 2014 at 09:48:18AM -0800, Toshio Kuratomi wrote: Packages for Infrastructure and Clouds, I think). I was thinking about this more recently in the context of things we need for Fedora.next in the coming

Re: EPEL Python 3.4 for 7

On Apr 27, 2014 9:37 AM, Aaron Knister aaron.knis...@gmail.com wrote: On Apr 26, 2014, at 8:58 PM, Toshio Kuratomi a.bad...@gmail.com wrote: On Apr 26, 2014 8:27 PM, Aaron Knister aaron.knis...@gmail.com wrote: We use both EPEL and SCL in my org. I didn't see this addressed in the email

EPEL RFC: Strategy for python3 versions

Hi guys, Orion has submitted a python34 package for EPEL and I'm going to review them soon if no one beats me to it. In parallel with getting that approved I'd like to ask about the general strategy we'd like to take with maintaining python3 in EPEL. Python3 is an evolving language. New 3.N

EPEL Orphan or retire the TurboGears (v1) stack in 7

Since RHEL7 has been released, EPEL7 won't be far behind. Before we get there, I'm planning to retire the TurboGears (v1, not Turbogears2) stack in epel7. In Fedora Infrastructure we are planning to migrate away from TurboGears1 rather than continue maintaining it throughout EPEL7's lifetime.

Re: EPEL Orphan or retire the TurboGears (v1) stack in 7

On Mon, Jun 16, 2014 at 12:01:26PM -0700, Toshio Kuratomi wrote: If someone steps up to say they'll take ownership of TurboGears1 (one of the comaintainers or someone new), then I'll reassign these packages to them. If no one does, then I'll retire them in epel7 and ask that the packages

Re: EPEL Orphan or retire the TurboGears (v1) stack in 7

-- Best Regards Jacky -Original Message- From: epel-devel-boun...@lists.fedoraproject.org [mailto:epel-devel-boun...@lists.fedoraproject.org] On Behalf Of Toshio Kuratomi Sent: Saturday, 21 June 2014 3:02 AM To: epel-devel@lists.fedoraproject.org Subject: Re: EPEL Orphan

Re: EPEL Orphan or retire the TurboGears (v1) stack in 7

On Fri, Jul 11, 2014 at 05:41:04PM +1000, Dan Callaghan wrote: I'm a little confused now though... I would have also expected these other TG1 pieces to be on the list: * python-TurboMail This doesn't have a dep on TurboGears in them so my repoquery didn't pick it up. Possibly a packaging

[EPEL-devel] Re: Which python3 versions to package for EPEL7?

On Tue, Jan 05, 2016 at 08:07:22PM -0700, Orion Poplawski wrote: > So, I've started packaging up a bunch of python3 only packages for EPEL7 for > packages that were already in RHEL7. I've started by packaging the latest > version of the modules: > > python34-py.noarch 1.4.30-2.el7

[EPEL-devel] Re: Virtual packages providing python2-*

On Tue, Feb 23, 2016 at 2:00 PM, Jason L Tibbitts III wrote: > One annoying difference between packaging for Fedora and EPEL7 (and > probably older) is the fact that Python packages in Fedora are required > to provide "python2-foo" whereas many EL7 packages don't. This leads

[EPEL-devel] Re: ansible retired in epel7

On Oct 7, 2017 1:18 PM, "Neal Gompa" wrote: On Tue, Oct 3, 2017 at 12:49 PM, Kevin Fenzi wrote: > Greetings. > > Just a note for anyone looking for ansible in epel7. > > It's been retired there because with the release of RHEL 7.4 it's now > int the

[EPEL-devel] Re: Python 3 packages to be removed form EPEL 7 (provided by RHEL 7)

On Tue, Jul 16, 2019, 3:48 PM Miro Hrončok wrote: > Hey, > > when RHEL 7.7 will be released, the following new components/packages will > be > provided (assuming from 7.7 beta): > > python3 - the Python 3.6 package > > > This new RHEL7 component builds several

[EPEL-devel] Re: ansible-core-2.11.x in CentOS stream 9

I believe ansible-core includes a "dependency manager" depending on your definition. The ansible-galaxy command in ansible-core can install ansible collections so that's you can install modules that you may need. It is similar in scope to pip, rubygem, cargo, or any other of the language package