PyPAM fails to build with Python 3.10.0a2.
PAMmodule.c:678:32: error: lvalue required as left operand of assignment
678 | Py_TYPE(&PyPAMObject_Type) = &PyType_Type;
At top level:
PAMmodule.c:10:13: warning: â€˜revisionâ€™ defined but not used [-Wunused-variable]
10 | static char revision = "$Id: PAMmodule.c,v 1.3 2007/04/18 03:55:11 rob Exp $";
error: command '/usr/bin/gcc' failed with exit code 1
error: Bad exit status from /var/tmp/rpm-tmp.wUHXmu (%build)
Since Py_TYPE() is changed to the inline static function, Py_TYPE(obj) = new_type must be replaced with Py_SET_TYPE(obj, new_type): see Py_SET_TYPE() (available since Python 3.9). For backward compatibility, this macro can be used:
#if PY_VERSION_HEX < 0x030900A4
# define Py_SET_TYPE(obj, type) ((Py_TYPE(obj) = (type)), (void)0)
For the build logs, see:
For all our attempts to build PyPAM with Python 3.10, see:
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.10:
Let us know here if you have any questions.
Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
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 change was reverted in Python 3.10, because it caused too much trouble (the amount of affected Fedora packages was too big). Keeping this open for now, unit anew alpha version is out to test it out.
This comment is mass posted in all relevant bugzillas. If you already worked upstream to fix the problem, please let them know about the revert.
I've patched Python 3.10 in our testing copr to include the revert. This package built fine. Sorry for the noise.