Bug 1629753

Fixed in Rawhide via https://koji.fedoraproject.org/koji/taskinfo?taskID=29762727

Note that our automation only determined python2-openstacksdk-tests as useless, not python2-openstacksdk.

python2-openstacksdk is unfortunately still required:

$ dnf repoquery --repo=rawhide --whatrequires python2-openstacksdk
python2-openstackclient-0:3.14.1-4.fc29.noarch
python2-openstacksdk-tests-0:0.12.0-3.fc29.noarch
python2-osc-lib-0:1.9.0-3.fc29.noarch
python2-shade-0:1.27.1-1.fc30.noarch

$ rdnf epoquery --repo=rawhide-source --whatrequires python2-openstacksdk
python-osc-lib-0:1.9.0-3.fc29.src
python-shade-0:1.27.1-1.fc30.src

If we can rid of that dependency (or those python2 packages), good. But if not, there is a problem.

The automation treats the packages as:

python2-openstackclient - keep, it has /usr/bin/openstack (can be run by Python 3 instead?)
python2-openstacksdk-tests - drop now
python2-osc-lib - drop later (needed by 21 packages)
python2-shade - keep, it has /usr/bin/shade-inventory-2.7 (maybe /usr/bin/shade-inventory from python3-shade is enough?)

Ok, I see.

I guess we should be able to remove all the python2 subpackages in the other packages, but I'll re-enable python2-openstacksdk for now, so we can do the fixes in order.

Before I open other bugs, would you be able to tell me what's the difference between:

 * /usr/bin/shade-inventory-X.Y running on py2 and py3
 * /usr/bin/openstack-X.Y running on py2 and py3

?

(In reply to Miro Hrončok from comment #4)
> Before I open other bugs, would you be able to tell me what's the difference
> between:
> 
>  * /usr/bin/shade-inventory-X.Y running on py2 and py3
>  * /usr/bin/openstack-X.Y running on py2 and py3
> 
> ?

They are the same binaries, running on different python versions.

https://koji.fedoraproject.org/koji/taskinfo?taskID=29763952 should be ok now. Can you check it?

(In reply to Javier Peña from comment #5)
> (In reply to Miro Hrončok from comment #4)
> > Before I open other bugs, would you be able to tell me what's the difference
> > between:
> > 
> >  * /usr/bin/shade-inventory-X.Y running on py2 and py3
> >  * /usr/bin/openstack-X.Y running on py2 and py3
> > 
> > ?
> 
> They are the same binaries, running on different python versions.

My question was more like: Is there a legitimate reason for the user to choose what Python versions the binaries run on?

E.g. for /usr/bin/pytest, the reason is that it runs test on the particular Python version. While e.g. /usr/bin/pygmentize is only shipped once because the user does not care what Python version it uses behind the scene.

(In reply to Javier Peña from comment #6)
> https://koji.fedoraproject.org/koji/taskinfo?taskID=29763952 should be ok
> now. Can you check it?

Seems OK.

(In reply to Miro Hrončok from comment #7)
> (In reply to Javier Peña from comment #5)
> > (In reply to Miro Hrončok from comment #4)
> > > Before I open other bugs, would you be able to tell me what's the difference
> > > between:
> > > 
> > >  * /usr/bin/shade-inventory-X.Y running on py2 and py3
> > >  * /usr/bin/openstack-X.Y running on py2 and py3
> > > 
> > > ?
> > 
> > They are the same binaries, running on different python versions.
> 
> My question was more like: Is there a legitimate reason for the user to
> choose what Python versions the binaries run on?
> 
> E.g. for /usr/bin/pytest, the reason is that it runs test on the particular
> Python version. While e.g. /usr/bin/pygmentize is only shipped once because
> the user does not care what Python version it uses behind the scene.
> 

Oh, I understand that now. No, there's no reason to choose which python version to the binary run on.

https://src.fedoraproject.org/rpms/python-openstackclient/pull-request/1

And https://src.fedoraproject.org/rpms/python-shade/pull-request/2