Description of problem: python-IPy fails to build on 32bit builders, causing random build failures depending on what builder koji randomly picks for the task. Looking at the build log, I fear the package doesn't even work on 32bit systems: + cd /builddir/build/BUILD + cd IPy-0.81 + PYTHONPATH=/builddir/build/BUILD/IPy-0.81 + /usr/bin/python2 test/test_IPy.py .......................................................................... ---------------------------------------------------------------------- Ran 74 tests in 0.061s OK + PYTHONPATH=/builddir/build/BUILD/IPy-0.81 + /usr/bin/python2 test_doc.py === Test file: README === === Test file: test.rst === === Test IPy module === === Overall Results === total tests 205, failures 0 + PYTHONPATH=/builddir/build/BUILD/IPy-0.81 + /usr/bin/python3 test/test_IPy.py .................................EE....................................... ====================================================================== ERROR: testNonZeroType (__main__.RegressionTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "test/test_IPy.py", line 861, in testNonZeroType self.assertEqual(bool(IPy.IP("0.0.0.0/0")), True) OverflowError: cannot fit 'int' into an index-sized integer ====================================================================== ERROR: testNulNetmask (__main__.RegressionTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "test/test_IPy.py", line 854, in testNulNetmask if ip: OverflowError: cannot fit 'int' into an index-sized integer ---------------------------------------------------------------------- Ran 74 tests in 0.063s FAILED (errors=2) RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.9imMMd (%check) Bad exit status from /var/tmp/rpm-tmp.9imMMd (%check) Child return code was: 1 Version-Release number of selected component (if applicable): python-IPy-0.81-20 How reproducible: Always Steps to Reproduce: 1. Build python-IPy-0.81-20 on a 32bit builder -- either in koji or mock 2. Watch it fail the abovementioned tests Actual results: It's broken :( Expected results: It's not broken! \o/ Additional info: Besides it probably affecting 32bit users, it also makes module builds that contain this package fail randomly.
Filed upstream: https://github.com/autocracy/python-ipy/issues/50
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.