Bug 2347197 - Please branch and build python-identify in epel10
Summary: Please branch and build python-identify in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-identify
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact:
URL:
Whiteboard:
Depends On: 2347198
Blocks: 2347199
TreeView+ depends on / blocked
 
Reported: 2025-02-23 18:27 UTC by Romain Geissler
Modified: 2025-02-26 01:23 UTC (History)
2 users (show)

Fixed In Version: python-identify-2.6.8-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-02-26 01:23:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Romain Geissler 2025-02-23 18:27:33 UTC
Hi,

Please branch and build python-identify in epel10.

I can help you co-maintaining the EPEL branches if you have no time for this request (fas id: romaingeissler1a).

Comment 1 Ben Beasley 2025-02-23 23:52:36 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=2347199#c1 regarding the dependency tree from python-ipykernel.

Comment 2 Fedora Update System 2025-02-24 17:36:49 UTC
FEDORA-EPEL-2025-f798838a57 (python-identify-2.6.8-1.el10_1 and python-ukkonen-1.0.1-16.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f798838a57

Comment 3 Fedora Update System 2025-02-25 02:40:25 UTC
FEDORA-EPEL-2025-f798838a57 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-f798838a57

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

Comment 4 Fedora Update System 2025-02-26 01:23:13 UTC
FEDORA-EPEL-2025-f798838a57 (python-identify-2.6.8-1.el10_1 and python-ukkonen-1.0.1-16.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.