Hi Please can a python-astroid package for EPEL8 be built. The current HEAD package can be built and installed with an EPEL 8 mock environment. However this is only after * python-lazy-object-proxy https://bugzilla.redhat.com/show_bug.cgi?id=1783304 * python3-typed_asthttps://bugzilla.redhat.com/show_bug.cgi?id=1783298 * python-wrapt https://bugzilla.redhat.com/show_bug.cgi?id=1783295 have been built and installed locally in the mock. Many Thanks Steve.
I have python-lazy-object-proxy and python3-typed_ast in the works, but I can't get tests to pass on epel8 of python-astroid from master, f31, f30, or f29. Did you make modifications?
Thanks for the action. I made no changes to any package and the tests executed okay.
Which versions of python-astroid and python-wrapt did you use?
Hi Gwyn, Reproduction: * fedpkg -a python-wrapt * cd python-wrapt * fedpkg srpm * mock -r epel-8-x86_64 --rebuild python-wrapt-1.11.2-4.fc32.src.rpm * cp /var/lib/mock/epel-8-x86_64/result/python3-wrapt-1.11.2-4.el8.x86_64.rpm . * mock -r epel-8-x86_64 --install ./python3-wrapt-1.11.2-4.el8.x86_64.rpm * cd .. * fedpkg -a python-astroid * cd python-astroid * fedpkg srpm * mock -r epel-8-x86_64 --rebuild ./python-astroid-2.3.3-2.gitace7b29.fc32.src.rpm --no-clean --enablerepo=testing ... astroid/tests/unittest_utils.py::InferenceUtil::test_if PASSED [ 99%] astroid/tests/unittest_utils.py::InferenceUtil::test_not_exclusive PASSED [ 99%] astroid/tests/unittest_utils.py::InferenceUtil::test_try_except PASSED [ 99%] astroid/tests/unittest_utils.py::InferenceUtil::test_unpack_infer_empty_tuple PASSED [ 99%] astroid/tests/unittest_utils.py::InferenceUtil::test_unpack_infer_uninferable_nodes PASSED [100%] ======== 824 passed, 65 skipped, 15 xfailed, 1 xpassed in 11.15 seconds ======== ... Finish: rpmbuild python-astroid-2.3.3-2.gitace7b29.fc32.src.rpm Finish: build phase for python-astroid-2.3.3-2.gitace7b29.fc32.src.rpm INFO: Done(./python-astroid-2.3.3-2.gitace7b29.fc32.src.rpm) Config(epel-8-x86_64) 0 minutes 32 seconds INFO: Results and/or logs in: /var/lib/mock/epel-8-x86_64/result Finish: run Never started vi once :-)
Weird. My local builds on CO8 fail. I'll see what happens in koji.
FEDORA-EPEL-2019-29a2054d6a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-29a2054d6a
python-astroid-2.3.3-2.gitace7b29.el8 has been pushed to the Fedora EPEL 8 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-2019-29a2054d6a
FEDORA-2020-177c2edb58 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-177c2edb58
FEDORA-EPEL-2020-22d337d626 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-22d337d626
python-astroid-2.3.3-4.gitace7b29.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
python-astroid-2.3.3-4.gitace7b29.el8 has been pushed to the Fedora EPEL 8 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-22d337d626
python-astroid-2.3.3-6.gitace7b29.el8, python-lazy-object-proxy-1.4.3-2.el8 has been pushed to the Fedora EPEL 8 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-8841b40fce
python-astroid-2.3.3-6.gitace7b29.el8, python-lazy-object-proxy-1.4.3-2.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.