Bug 1873104

Summary: patchelf 0.12 is available
Product: [Fedora] Fedora Reporter: Avi Kivity <avi.kivity>
Component: patchelfAssignee: Jeremy Sanders <jeremy>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: jeremy, ppisar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: patchelf-0.12-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-27 15:17:28 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 Avi Kivity 2020-08-27 11:45:23 UTC
Description of problem:

patchelf 0.12 is available, with several fixes.


Version-Release number of selected component (if applicable):
N/A


Additional info:

https://github.com/NixOS/patchelf/releases/tag/0.12

Comment 1 Fedora Update System 2020-08-27 15:13:19 UTC
FEDORA-2020-44175fcbf3 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-44175fcbf3

Comment 2 Jeremy Sanders 2020-08-27 15:17:28 UTC
The above release should fix this bug. Please reopen if there's a problem with the update.

Comment 3 Fedora Update System 2020-08-28 14:55:03 UTC
FEDORA-2020-44175fcbf3 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-44175fcbf3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-44175fcbf3

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

Comment 4 Fedora Update System 2020-09-05 18:31:29 UTC
FEDORA-2020-44175fcbf3 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.