libtdb fails to build with Python 3.13.0a6.
+ ./configure --build=x86_64-redhat-linux --host=x86_64-redhat-linux --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-rpath --bundled-libraries=NONE --builtin-libraries=replace
Traceback (most recent call last):
  File "/builddir/build/BUILD/tdb-1.4.10/third_party/waf/waflib/Scripting.py", line 159, in waf_entry_point
    run_commands()
    ~~~~~~~~~~~~^^
  File "/builddir/build/BUILD/tdb-1.4.10/third_party/waf/waflib/Scripting.py", line 251, in run_commands
    parse_options()
    ~~~~~~~~~~~~~^^
  File "/builddir/build/BUILD/tdb-1.4.10/third_party/waf/waflib/Scripting.py", line 217, in parse_options
    ctx.execute()
    ~~~~~~~~~~~^^
  File "/builddir/build/BUILD/tdb-1.4.10/third_party/waf/waflib/Options.py", line 358, in execute
    Utils.alloc_process_pool(options.jobs)
                             ^^^^^^^^^^^^
AttributeError: 'Values' object has no attribute 'jobs'

https://docs.python.org/3.13/whatsnew/3.13.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/07302767-libtdb/

For all our attempts to build libtdb with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/libtdb/

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

Let us know here if you have any questions.

Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13.
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.