Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1896684 - duplicity fails to build with Python 3.10: Py_TYPE= needs to be replaced with Py_SET_TYPE
Summary: duplicity fails to build with Python 3.10: Py_TYPE= needs to be replaced with...
Alias: None
Product: Fedora
Classification: Fedora
Component: duplicity
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: PYTHON3.10
TreeView+ depends on / blocked
Reported: 2020-11-11 09:22 UTC by Tomáš Hrnčiar
Modified: 2020-11-18 17:59 UTC (History)
4 users (show)

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

Attachments (Terms of Use)

Description Tomáš Hrnčiar 2020-11-11 09:22:35 UTC
duplicity fails to build with Python 3.10.0a2.

duplicity/_librsyncmodule.c: In function ‘moduleinit’:
duplicity/_librsyncmodule.c:467:36: error: lvalue required as left operand of assignment
  467 |   Py_TYPE(&_librsync_SigMakerType) = &PyType_Type;
      |                                    ^
duplicity/_librsyncmodule.c:468:38: error: lvalue required as left operand of assignment
  468 |   Py_TYPE(&_librsync_DeltaMakerType) = &PyType_Type;
      |                                      ^

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 duplicity 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.

Comment 1 Gwyn Ciesla 2020-11-11 18:34:42 UTC
Sending patch upstream.

Comment 2 Miro Hrončok 2020-11-18 17:59:13 UTC
JFYI The change was reverted in Python 3.10, because it caused too much trouble (the amount of affected Fedora packages was too big).

This comment is mass posted in all relevant bugzillas. If you already worked upstream to fix the problem, you might want to let them know about the revert, but the new way of doing things also works.

Sorry for the trouble and thanks again for the fix.

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