Bug 2430515 - Please branch and build python-stone in epel10
Summary: Please branch and build python-stone in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-stone
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2407403
TreeView+ depends on / blocked
 
Reported: 2026-01-16 21:10 UTC by Simon de Vlieger
Modified: 2026-01-31 17:47 UTC (History)
1 user (show)

Fixed In Version: python-stone-3.2.1-22.el10_2
Clone Of:
Environment:
Last Closed: 2026-01-31 17:47:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Simon de Vlieger 2026-01-16 21:10:21 UTC 
Hi, we'd like to package duplicity in epel10 and this package is one of its dependencies. Could you branch and build python-stone in epel10?

If you don't want to maintain python-stone 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-stone/adduser


Reproducible: Always
Comment 1 Fedora Update System 2026-01-21 15:22:45 UTC 
FEDORA-EPEL-2026-d669284e83 (python-stone-3.2.1-22.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d669284e83
Comment 2 Fedora Update System 2026-01-22 01:20:28 UTC 
FEDORA-EPEL-2026-d669284e83 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-d669284e83

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-01-31 17:47:56 UTC 
FEDORA-EPEL-2026-d669284e83 (python-stone-3.2.1-22.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.