Description of problem:
Python3-libs should not depend on /usr/bin/python3.6:
$ rpm -qR python3-libs
... snip ...
... snip ...
If this dependency is really required, then the split of -libs package makes no sense.
Version-Release number of selected component (if applicable):
$ rpm -q python3-libs
Steps to Reproduce:
python3-libs depends on /usr/bin/python3.6 and therefore on python3 package.
python3-libs does not depend on python3 package
On my Fedora 27, following files have the shebang that pulls the dependency:
Those files are executable and have a "main part" that gets run when executed. I however wonder how beneficial this actually is and how many users need to execute them.
I doubt anyone would call `/usr/lib64/python3.6/keyword.py` rather than `python3 -m keyword`.
But, I guess that's an upstream issue (and earliest we can get it in there is 3.8).
Should we only recommend /usr/bin/python3, instead of requiring it? That would make sense to me. Runnable scripts are not the main-purpose of python3-libs and the error message of missing python3 is nice and actionable. But, things stand, you do need python3 to get the full functionality.
Filtering the autogenerated "Requires: /usr/bin/python3.6" replacing it by Recommends makes sense to me.
PR for python37 https://src.fedoraproject.org/rpms/python37/pull-request/7
Given the severity of this, I don't consider backporting to stable Fedoras necessary. Feel free to reopen if you disagree.
Thx for fixing this. The buildroot is slimmer by ~3 packages due to this change.
Do you know what pulls python3-libs into the buildroot and whether it works without python3?
It appears to be gdb-headless.