python-systemd fails to build in Copr. ____________________________ test_notify_no_socket _____________________________ def test_notify_no_socket(): > assert notify('READY=1') is False E PermissionError: [Errno 13] Permission denied systemd/test/test_daemon.py:260: PermissionError We add this to our Python 3.9 builds: TESTFLAGS="-k 'not test_notify_no_socket'" Could the test suite please be adapted to skip this test when the permissions are not satisfactory? It would make stuff easier for us. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
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.
The following builds were made after this report was opened: python-systemd-234-13.fc33 python-systemd-234-14.fc33
Sorry for the noise, removing the F33FTBFS tracker from here.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Built in rawhide.