Description of problem: The python2 subpackage "python-execnet" does not depend on python-apipkg, so we cannot import execnet with Python 2. Version-Release number of selected component (if applicable): python-execnet-1.7.1-2.el7 How reproducible: always Steps to Reproduce: 1. Start with an EL7 machine that does *not* have python-apipkg installed 2. yum -y install python-execnet 3. Try to import execnet, for example: python -c "import execnet" Actual results: Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python2.7/site-packages/execnet/__init__.py", line 10, in <module> import apipkg ImportError: No module named apipkg Expected results: "yum install python-execnet" should install python-apipkg. python -c "import execnet" should work without errors. Additional info: We fixed this for Python 3 in https://src.fedoraproject.org/rpms/python-execnet/pull-request/6 , and we forgot to fix this for Python 2.
Ken, thanks for fixing this: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1ccdc325aa
You're welcome! Bodhi did not comment on this bug yet, and I filed https://github.com/fedora-infra/bodhi/issues/3954 for that problem. Thanks for linking to the update here.
python-execnet-1.7.1-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1ccdc325aa
python-execnet-1.7.1-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.