Bug 2439330 - Please branch and build osc in epel10
Summary: Please branch and build osc in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: osc
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: 2026-02-12 14:19 UTC by mmassari
Modified: 2026-02-20 00:40 UTC (History)
5 users (show)

Fixed In Version: osc-1.22.0-465.2.2.el10_2
Clone Of:
Environment:
Last Closed: 2026-02-20 00:40:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description mmassari 2026-02-12 14:19:03 UTC 
Please branch and build osc in epel10.

We have been asked to build packit in epel10 and packit needs osc.

If you do not wish to maintain osc 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/osc/adduser
Comment 1 Miroslav Suchý 2026-02-12 20:53:41 UTC 
https://koji.fedoraproject.org/koji/taskinfo?taskID=142230034
Comment 2 Fedora Update System 2026-02-12 20:55:15 UTC 
FEDORA-EPEL-2026-baf63db46a (osc-1.22.0-465.2.2.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-baf63db46a
Comment 3 Fedora Update System 2026-02-13 01:07:05 UTC 
FEDORA-EPEL-2026-baf63db46a 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-baf63db46a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2026-02-20 00:40:17 UTC 
FEDORA-EPEL-2026-baf63db46a (osc-1.22.0-465.2.2.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.