Bug 2369144 - Please branch and build python-marshmallow in epel10.
Summary: Please branch and build python-marshmallow in epel10.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-marshmallow
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-29 09:42 UTC by mmassari
Modified: 2025-06-08 00:30 UTC (History)
4 users (show)

Fixed In Version: python-marshmallow-3.25.0-2.el10_1
Clone Of:
Environment:
Last Closed: 2025-06-08 00:30:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description mmassari 2025-05-29 09:42:45 UTC
Please branch and build python-marshmallow in epel10.

We have been asked to build packit in epel10 :)

If you do not wish to maintain python-marshmallow in epel10,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS mmassari);
please add me through https://src.fedoraproject.org/rpms/python-marshmallow/adduser

Comment 1 Fedora Update System 2025-05-30 05:26:55 UTC
FEDORA-EPEL-2025-5d3c1130cb (python-marshmallow-3.25.0-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5d3c1130cb

Comment 2 Fedora Update System 2025-05-31 01:40:58 UTC
FEDORA-EPEL-2025-5d3c1130cb has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5d3c1130cb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2025-06-08 00:30:04 UTC
FEDORA-EPEL-2025-5d3c1130cb (python-marshmallow-3.25.0-2.el10_1) has been pushed to the Fedora EPEL 10.1 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.