Bug 2419738 - Please branch and build libharu in epel10
Summary: Please branch and build libharu in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libharu
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dmitrij S. Kryzhevich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2419727
TreeView+ depends on / blocked
 
Reported: 2025-12-07 02:05 UTC by Orion Poplawski
Modified: 2026-03-24 02:12 UTC (History)
1 user (show)

Fixed In Version: libharu-2.4.5-1.el10_2 libharu-2.4.5-1.el10_3 libharu-2.4.5-1.el10_1
Clone Of:
Environment:
Last Closed: 2026-03-24 02:02:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2025-12-07 02:05:23 UTC
Please branch and build libharu in epel10 (and epel10.1, 10.0)

If you do not wish to maintain libharu 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 orion);
please add me through https://src.fedoraproject.org/rpms/libharu/adduser

It appears to build fine.

Comment 1 Orion Poplawski 2026-02-21 18:29:28 UTC
Will you be able to branch and build libharu in epel10?
I would be happy to be a co-maintainer if you do not wish
to build it on epel10 (FAS: orion).

Comment 2 Dmitrij S. Kryzhevich 2026-03-13 05:10:47 UTC
Branch done.
Package was built.
Anyway commit access applied.

My appologies.

Comment 3 Fedora Update System 2026-03-13 05:11:03 UTC
FEDORA-EPEL-2026-76ab3a6a37 (libharu-2.3.0-10.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-76ab3a6a37

Comment 4 Orion Poplawski 2026-03-14 04:28:37 UTC
Why did you build 2.3.0 rather than 2.4.5?

Comment 5 Fedora Update System 2026-03-15 14:12:07 UTC
FEDORA-EPEL-2026-7302a3628e (libharu-2.4.5-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7302a3628e

Comment 6 Fedora Update System 2026-03-15 14:12:08 UTC
FEDORA-EPEL-2026-9b6072fc1b (libharu-2.4.5-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-9b6072fc1b

Comment 7 Fedora Update System 2026-03-16 02:02:45 UTC
FEDORA-EPEL-2026-9b6072fc1b 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-9b6072fc1b

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

Comment 8 Fedora Update System 2026-03-16 02:04:56 UTC
FEDORA-EPEL-2026-ce9fc8591d has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-ce9fc8591d

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

Comment 9 Fedora Update System 2026-03-16 02:12:04 UTC
FEDORA-EPEL-2026-7302a3628e 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-2026-7302a3628e

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

Comment 10 Fedora Update System 2026-03-24 02:02:58 UTC
FEDORA-EPEL-2026-9b6072fc1b (libharu-2.4.5-1.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.

Comment 11 Fedora Update System 2026-03-24 02:04:52 UTC
FEDORA-EPEL-2026-ce9fc8591d (libharu-2.4.5-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2026-03-24 02:12:19 UTC
FEDORA-EPEL-2026-7302a3628e (libharu-2.4.5-1.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.