Bug 1918537

Summary: Please build urdfdom-headers for EPEL 8
Product: [Fedora] Fedora EPEL Reporter: Scott K Logan <logans>
Component: urdfdom-headersAssignee: Rich Mattes <richmattes>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: richmattes, robotics
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: urdfdom-headers-1.0.5-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-15 00:16:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Scott K Logan 2021-01-21 00:46:52 UTC
Description of problem:
The urdfdom-headers package is built for EPEL 7, but there is no build for EPEL 8.

I found that the current rawhide branch builds successfully against EPEL 8, except for a small part of the Fedora patch that was updated in the latest release for Fedora.

Comment 1 Rich Mattes 2021-02-22 18:53:24 UTC
Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/32276

Comment 2 Fedora Update System 2021-02-27 19:48:12 UTC
FEDORA-EPEL-2021-56f9b1b656 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-56f9b1b656

Comment 3 Fedora Update System 2021-02-27 22:10:05 UTC
FEDORA-EPEL-2021-56f9b1b656 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-56f9b1b656

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

Comment 4 Fedora Update System 2021-03-15 00:16:39 UTC
FEDORA-EPEL-2021-56f9b1b656 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.