Bug 1897529 - pylibacl fails to build with Python 3.10: Py_TYPE= needs to be replaced with Py_SET_TYPE
Summary: pylibacl fails to build with Python 3.10: Py_TYPE= needs to be replaced with ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pylibacl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marcin Zajaczkowski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.10
TreeView+ depends on / blocked
 
Reported: 2020-11-13 11:13 UTC by Tomáš Hrnčiar
Modified: 2020-11-18 19:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-18 19:47:15 UTC
Type: Bug


Attachments (Terms of Use)

Description Tomáš Hrnčiar 2020-11-13 11:13:45 UTC
pylibacl fails to build with Python 3.10.0a2.

acl.c:1803:24: error: lvalue required as left operand of assignment
 1803 |     Py_TYPE(&ACL_Type) = &PyType_Type;
      |                        ^
acl.c:1808:26: error: lvalue required as left operand of assignment
 1808 |     Py_TYPE(&Entry_Type) = &PyType_Type;
      |                          ^
acl.c:1812:28: error: lvalue required as left operand of assignment
 1812 |     Py_TYPE(&Permset_Type) = &PyType_Type;
      |                            ^
error: command '/usr/bin/gcc' failed with exit code 1
error: Bad exit status from /var/tmp/rpm-tmp.koiMBv (%build)

https://docs.python.org/3.10/whatsnew/3.10.html#id2

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)
#endif
https://bugs.python.org/issue39573

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.10/fedora-rawhide-x86_64/01757246-pylibacl/

For all our attempts to build pylibacl with Python 3.10, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.10/package/pylibacl/

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:
https://copr.fedorainfracloud.org/coprs/g/python/python3.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.

Comment 1 Marcin Zajaczkowski 2020-11-13 19:21:48 UTC
Luckily, upstream is testing it automatically [1] with different Python versions (including nightly) and it was already detected and fixed [2]:

[1] - https://travis-ci.org/github/iustin/pylibacl/builds/742139329
[2] - https://github.com/iustin/pylibacl/commit/26712b8fd92f1146102248cac1c92cb344620eff

If you are up to date with the project you might provide a pull request with that change as a patch. Alternatively, I will handle that in the following days.

Comment 2 Miro Hrončok 2020-11-18 17:57:16 UTC
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.

https://github.com/python/cpython/commit/0e2ac21dd

Comment 3 Miro Hrončok 2020-11-18 19:47:15 UTC
I've patched Python 3.10 in our testing copr to include the revert. This package built fine. Sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.