[EPEL-devel] Re: Python 3.7 in EPEL?
On Dec 11, 2019, at 17:33, Stephen John Smoogen wrote: > I want to correct one thing: EPEL is not an Enterprise repository. It > is a nearly complete volunteer effort and things will add and > disappear over time as volunteers come in and out. We try to make it > stable and useful but we do not guarantee/promise/etc any Enterprise > level 'support'. If you are needing that then I would contract out for > it with someone who can do that kind of work... or come up with > techniques to mitigate changes that will occur in EPEL. Thank you for the clarification. Very good to know! Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-|___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: Python 3.7 in EPEL?
On Dec 11, 2019, at 12:50, Stephen John Smoogen wrote: > The issue is that most 'users' of the language do not see a difference > between the 2. When they say python3x they mean > python3x+whatever-bits-i-needed. So as soon as you put in the > interpreter.. then comes the 'why isn't python37-x there? etc etc' IIRC, that is exactly what happened with the 3.4 => 3.6 transition. What made that particularly painful for me was that the 3.4 versions of many of the dependent bits suddenly went away, to be *replaced* (rather than augmented) by 3.6 ones. This caused major disruption in a number of projects that I maintain that had formal dependencies on the 3.4 bits. Will this same thing happen to the 3.6 bits if we add 3.7? If so, then I would strongly oppose making the addition. Having packages spontaneously disappear seems to contradict the whole point of having an ‘Enterprise’ distro. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Thu, 2019-05-02 at 11:42 -0700, Kevin Fenzi wrote:
> Well, you can specify directly /usr/bin/python3.4 if you need
> specifially python3.4.
Yes, that is what I've started doing. Effectively, we've pinned it to
3.4.
> If you only specified 'python3' in theory either
> one should work for that.
Unfortunately, that breaks if the local user has created modules of his
own --i.e. not under management by rpm(8)-- and placed them in
'%{_libdir}/python3.4/'. That's actually a pretty common scenario in
our use case!
Cheers!
|-|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero |
|-|
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Thu, 2019-05-02 at 10:26 -0700, Kevin Fenzi wrote: > Sorry this is all so confusing. ;( Life can be complicated at times! :) I admit that the way this Python 3.4 => 3.6 update worked suprised me. I have binary packages that depend on several python34-* packages. The update broke those in a couple of ways; not only by the disappearance of the pycurl and mysql pieces, but by the fact that '/usr/bin/python3' got changed to point to '/usr/bin/python3.6' rather than '/usr/bin/python3.4'. What is best practice for specifying Python dependencies so that they will survive this sort of thing? Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Thu, 2019-05-02 at 19:23 +0200, Miro Hrončok wrote: > File RFE bugzillas against python3-mysql: Done. https://bugzilla.redhat.com/show_bug.cgi?id=1705679 > Or/and python3-pycurl: https://bugzilla.redhat.com/show_bug.cgi?id=1705680 Thanks. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Wed, 2019-05-01 at 16:17 -0700, Kevin Fenzi wrote: > Can you please refile that as two bugs? On python3-pycurl and > python3-mysql? > > The python34 component is only for python34 itself, you will need to > get > those other two packages to fix things. I did attempt this initially, but the 'Component' field refuses to accept 'python34-mysql' or 'python34-pycurl' as a valid value. What should the proper value there be? Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Tue, 2019-04-30 at 15:17 -0700, Troy Dawson wrote: > What to do? > Open a bugzilla on the package, requesting that it be fixed so it > builds for both versions of python. Submitted on BugZilla: https://bugzilla.redhat.com/show_bug.cgi?id=1705286 Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | There is only one thing worse than having your competitors trying | | to inter-operate with your systems - and that is to have your | | competitors *not* trying to inter-operate with your systems. | | | | -- Alan(UK), GrokLaw.net | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?
On Tue, 2019-04-30 at 15:17 -0700, Troy Dawson wrote: > It all depended on the person who created the package. > If the package was written to only build for the lastest python > package (python3_pkgversion), then that package only has > python36- now. > If it was written so that it builds for the latest, and "other" > python > version (python3_other_pkgversion), then that package now has > python34- and python36- Thank you. That makes perfect sense. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] What happened to the 'python34-pycurl' and 'python34-mysql' packages?
Greetings! I am attempting to ascertain the current status of the 'python34- pycurl' and 'python34-mysql' packages on EPEL for RHEL7. It appears that these may have gone missing around the time of the addition of the 'python36-' packages about a month ago. Were these packages withdrawn intentionally? Curiously, I can still see numerous other 'python34-' packages --i.e. 'python34-requests' -- as being available. I can also see that 'python36-pycurl' and 'python36-mysql' packages both currently exist. Any assistance greatly appreciated! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-| ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
