python-bsddb3 fails to build with Python 3.11.0a1. Traceback (most recent call last): File "/builddir/build/BUILD/bsddb3-6.2.9/test3.py", line 153, in <module> from unittest.runner import _TextTestResult ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ImportError: cannot import name '_TextTestResult' from 'unittest.runner' (/usr/lib64/python3.11/unittest/runner.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/builddir/build/BUILD/bsddb3-6.2.9/test.py", line 42, in <module> import test3 as test ^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/bsddb3-6.2.9/test3.py", line 155, in <module> from unittest import _TextTestResult ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ImportError: cannot import name '_TextTestResult' from 'unittest' (/usr/lib64/python3.11/unittest/__init__.py) Removed many old deprecated unittest features: An alias of the TextTestResult class: _TextTestResult (deprecated in Python 3.2). (Contributed by Serhiy Storchaka in bpo-45162.) https://bugs.python.org/issue45162 https://docs.python.org/3.11/whatsnew/3.11.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.11/fedora-rawhide-x86_64/02909796-python-bsddb3/ For all our attempts to build python-bsddb3 with Python 3.11, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/package/python-bsddb3/ 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.11: https://copr.fedorainfracloud.org/coprs/g/python/python3.11/ Let us know here if you have any questions. Python 3.11 is already included in Fedora 35. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.11. 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 upstream now considers the bsddb3 package to be legacy, replaced with berkeleydb package (not yet in Fedora) – see https://www.jcea.es/programacion/pybsddb.htm for details. I can try to package the new package for Fedora and start the package replacement process; however, I'm no longer interacting with BerkeleyDB in my line of work, and I was essentially maintaining the python-bsddb3 package only because of "inertia" and because it was usually not too much of a trouble. So, I would not be opposed to someone from the python team or the libdb maintainer taking this over :)
> I would not be opposed to someone from the python team [...] taking this over :) The Python team is not interested in maintaining random Python packages. The following packages require python3-bsddb3: exaile (runtime and buildtime) gramps (runtime) python-zarr (buildtime only) I suggest talking to the maintainers of those packages and/or orphaning python-bsddb3.
(In reply to Miro Hrončok from comment #2) > The Python team is not interested in maintaining random Python packages. Reasonable, acknowledged. > I suggest talking to the maintainers of those packages and/or orphaning > python-bsddb3. I reached to the maintainer of libdb, let's see where this goes.
Since Libdb has no upstream support and was marked as deprecated I would recommend orphaning it.
The package was now orphaned.
https://gramps-project.org/bugs/view.php?id=12305
python-berkeleydb is now in f36+
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.