Hi, we'd like to package duplicity in epel10 and this package is one of its dependencies. Could you branch and build python-b2sdk in epel10? If you don't want to maintain python-b2sdk in epel10 or don't think you'll be able to do this in a timely manner I would be happy to be a co-maintainer of the package (FAS: supakeen). You can add me through https://src.fedoraproject.org/rpms/python-b2sdk/adduser Reproducible: Always
Scratch build succeeds, please add me (limb) as a maintainer and I can take care of it.
Added you both as maintainers
Thank you!
FEDORA-EPEL-2026-32853e2c9d (python-b2sdk-1.21.0-13.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-32853e2c9d
FEDORA-EPEL-2026-32853e2c9d has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-32853e2c9d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Regarding the missing logfury dependency, porting the spec file to the modern pyproject macros (bug 2377501) will help identify missing runtime requirements because it marks those as build time requirements by default. It's also helpful to run an import check and upstream unit tests whenever possible. Here is a pull request to do both of those things. https://src.fedoraproject.org/rpms/python-b2sdk/pull-request/1 I would also highly recommend updating this package to the latest version before adding it to EPEL 10. EPEL update policy doesn't allow making disruptive changes during a major version, so it would be best to start on the most recent version possible. https://docs.fedoraproject.org/en-US/epel/epel-policy/