Created attachment 1714695 [details] build.log from Koji Description of problem: Package marshalparser fails to build from source on s390x. I suspect any big endidan. Version-Release number of selected component: 0.2.0-1.fc33 Steps to Reproduce: fedpkg build --scratch --arches s390x Additional info: This package is tracked by Koschei. See: https://koschei.fedoraproject.org/package/marshalparser Traceback (most recent call last): File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code exec(code, run_globals) File "/builddir/build/BUILD/marshalparser-0.2.0/marshalparser/__main__.py", line 3, in <module> main() File "/builddir/build/BUILD/marshalparser-0.2.0/marshalparser/marshalparser.py", line 373, in main parser.parse() File "/builddir/build/BUILD/marshalparser-0.2.0/marshalparser/marshalparser.py", line 57, in parse self.read_object() File "/builddir/build/BUILD/marshalparser-0.2.0/marshalparser/marshalparser.py", line 150, in read_object result.append(self.read_object()) File "/builddir/build/BUILD/marshalparser-0.2.0/marshalparser/marshalparser.py", line 96, in read_object i, b = next(self.iterator) StopIteration Full build.log attached.
byteorder should always be 'little', not system-dependent
https://github.com/fedora-python/marshalparser/pull/5
FEDORA-2020-bd566a98a5 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bd566a98a5
FEDORA-2020-bd566a98a5 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bd566a98a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bd566a98a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-bd566a98a5 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.