What happened to the 'python34-pycurl' and 'python34-mysql' packages?

[Fred Gleason]

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   |
|---------------------------------------------------------------------|

[Miro Hrončok]

On 30. 04. 19 22:41, Fred Gleason wrote:
> 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.

Yes, with the transition form 3.4 to 3.6, some python34 packages are gone.

Some packages build for both versions (such as requests), some only build for 
the "primary version". That changed from 3.4 to 3.6.

I suggest to migrate to Python 3.6. If you indeed need those packages, file RFE 
bugzillas against python3-mysql:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&version=...

Or/and python3-pycurl:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&version=...

[Troy Dawson]

On Tue, Apr 30, 2019 at 1:41 PM Fred Gleason  wrote:
> 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!

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-<package> 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-<package> and python36-<package>

What to do?
Open a bugzilla on the package, requesting that it be fixed so it
builds for both versions of python.

Troy Dawson

[Fred Gleason]

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-<package> 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-<package> and python36-<package>

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   |
|---------------------------------------------------------------------|

[Fred Gleason]

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   |
|---------------------------------------------------------------------|

[Kevin Fenzi]

On 5/1/19 3:21 PM, Fred Gleason wrote:
> 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

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.

Thanks,

kevin

[Fred Gleason]

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   |
|---------------------------------------------------------------------|

[Miro Hrončok]

On 02. 05. 19 19:10, Fred Gleason wrote:
> 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?

From my previous e-mail:

File RFE bugzillas against python3-mysql:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&version=...

Or/and python3-pycurl:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&version=...

[Kevin Fenzi]

On 5/2/19 10:10 AM, Fred Gleason wrote:
> 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?

python3-mysql and python3-pycurl

Those source packages make (currently) the python36-mysql and
python36-pycurl binary packages.

Sorry this is all so confusing. ;(

kevin

[Todd Zullinger]

Hi,

Fred Gleason wrote:
> 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?

The source packages for the python3X-* packages are
generally python3-* and those are what are used in the
bugzilla component field.

So these should be under python3-mysql and python3-pycurl,
respectively (which looks like what Kevin suggested :) ).

[Fred Gleason]

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   |
|---------------------------------------------------------------------|

[Fred Gleason]

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   |
|---------------------------------------------------------------------|

[Kevin Fenzi]

On 5/2/19 11:28 AM, Fred Gleason wrote:
> 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?

Well, you can specify directly /usr/bin/python3.4 if you need
specifially python3.4. If you only specified 'python3' in theory either
one should work for that.

kevin

[Fred Gleason]

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   |
|---------------------------------------------------------------------|