gpaw fails to build with Python 3.9.0a6. Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Jznumu + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/gpaw-19.8.1-6.fc33.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/gpaw-19.8.1-6.fc33.x86_64 ++ dirname /builddir/build/BUILDROOT/gpaw-19.8.1-6.fc33.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/gpaw-19.8.1-6.fc33.x86_64 + cd gpaw-19.8.1 + sed -i 's/.*scalapack =.*/scalapack = False/' python3/customize.py + sed -i 's/compiler = "mpicc"/#compiler = "mpicc"/' python3/customize.py + sed -i 's|.*hdf5 =.*|#hdf5 = False|' python3/customize.py + pushd python3 ~/build/BUILD/gpaw-19.8.1/python3 ~/build/BUILD/gpaw-19.8.1 + mv build_serial build mv: cannot stat 'build_serial': No such file or directory Seems like there is some build failure before this, but I couldn't find it in the log. For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01365850-gpaw/ For all our attempts to build gpaw with Python 3.9, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/gpaw/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ Let us know here if you have any questions. Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
The message above mentions ``` For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01365850-gpaw/ ``` but this returns 404. About the "gpaw fails to build with Python 3.9" issue itself - the build probably failed due to libxc5. I can build gpaw with python 3.9 but the resulting build is not fully functional. Added the relevant bug as a dependency.
The 404 error is caused by a garbage collector. I've triggered a new build, sorry about that.
This comment is mass posted to all bugs blocking the Python 3.9 tracker, sorry if it is not 100 % relevant. When in doubt, please ask. The Python 3.9 rebuild is in progress in a Koji side tag. If you fix this bug, please don't rebuild the package in regular rawhide, but do it in the side tag with: $ fedpkg build --target=f33-python The rebuild is progressing slowly and it is possible this package won't have all the required build dependencies yet. If that's the case, please just leave the fix committed and pushed and we will eventually rebuild it for you. You are not asked to go and try rebuild all the missing dependencies yourself. If you know there is a bootstrap loop in the dependencies, let me know and we can untangle it together. If you want to test your fix or reproduce the failure, you can still use the Copr repo mentioned in the initial comment of this bug: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/
Python 3.9 update: The f33-python side tag is currently being merged. New builds in f33-python are no longer possible, but python3 is not yet updated to Python 3.9 in rawhide. You can check when Python is Python 3.9 with: $ koji wait-repo f33-build --build python3.9-3.9.0~b1-3.fc3 And build the packages normally after that.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Hello. This comment is mass posted to all 16 bugzillas for packages that failed to rebuild with Python 3.9 (and, in most cases, also fail to install on Fedora 33 and 34). Apologies if some of the suggestions or questions don't apply 100%. Fedora 33 Beta Freeze starts next week on Tuesday, 2020-08-25. I haven't spammed this bugzilla because it is in ASSIGNED, or I've seen upstream has been notified. Please consider what to do here. Is this failure critical? For example, can a test be temporarily skipped to make this package build? Is it possible to fix or workaround the failure before Fedora 33 Beta? Or before Fedora 33 Final? If not, would it make sense to retire the package (even temporarily) before the release to unblock updates from Fedora 31 or Fedora 32? In case you need any assistance with a Python-related problem with the build, don't hesitate to let me know and I'll try to have a look. Thank you!
I've been able to build a version, which however has a broken functionality meaning the outputs from the program may be wrong. I'm not sure how to proceed from here. The rawhide f34 build is here https://koji.fedoraproject.org/koji/taskinfo?taskID=50897701
FEDORA-2020-9878f86205 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9878f86205
Proposed as a Freeze Exception for 33-beta by Fedora user churchyard using the blocker tracking app because: The package does not install without the proposed update.
FEDORA-2020-c472913d60 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c472913d60
FEDORA-2020-9878f86205 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-9878f86205` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9878f86205 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Accepted as a Beta freeze exception: https://pagure.io/fedora-qa/blocker-review/issue/75
FEDORA-2020-9878f86205 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.