Bug 2332652 - Please branch and build libdwarf in epel10
Summary: Please branch and build libdwarf in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libdwarf
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-16 20:17 UTC by Christoph Erhardt
Modified: 2024-12-27 00:32 UTC (History)
4 users (show)

Fixed In Version: libdwarf-0.11.1-1.el10_0
Clone Of:
Environment:
Last Closed: 2024-12-27 00:32:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christoph Erhardt 2024-12-16 20:17:46 UTC
Please branch and build libdwarf in epel10.

I would like to package mold (a modern linker), which has a build dependency on libdwarf-tools, for epel10.

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

Comment 1 Orion Poplawski 2024-12-17 00:37:14 UTC
I've added you to the package.  Thanks.

Comment 2 Fedora Update System 2024-12-18 21:00:18 UTC
FEDORA-EPEL-2024-b496da512c (libdwarf-0.11.1-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b496da512c

Comment 3 Fedora Update System 2024-12-19 00:22:05 UTC
FEDORA-EPEL-2024-b496da512c has been pushed to the Fedora EPEL 10.0 testing repository.

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

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

Comment 4 Fedora Update System 2024-12-27 00:32:25 UTC
FEDORA-EPEL-2024-b496da512c (libdwarf-0.11.1-1.el10_0) has been pushed to the Fedora EPEL 10.0 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.