Bug 1929735

Summary: Updated bundled libbacktrace for DWARF5
Product: [Fedora] Fedora Reporter: Mark Wielaard <mjw>
Component: R-winchAssignee: Elliott Sales de Andrade <quantum.analyst>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: law, quantum.analyst
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-08 00:32:07 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 Mark Wielaard 2021-02-17 14:27:42 UTC
GCC11 in Fedora 34 defaults to producing DWARF5. This requires an update of libbacktrace which is bundled in this package.

Comment 1 Elliott Sales de Andrade 2021-02-25 00:42:41 UTC
I'm aware of that, but my scratch build attempting to patch it in still fails on other arches in essentially the same way as before.

Comment 2 Jeff Law 2021-02-25 17:47:10 UTC
FWIW, I've sync'd libbacktrace/dwarf.c with upstream and fixed the MD5 file.  That seems to have done the trick on my scratch builds.  I'm spinning official ones right now.

I do think that a full sync of libbacktrace is advisable though, particularly for rawhide.

Comment 3 Elliott Sales de Andrade 2021-02-27 10:52:47 UTC
OK, my scratch build was patched with HEAD from https://github.com/ianlancetaylor/libbacktrace; apparently even though that's recently updated with history that looks quite similar, it's not in sync with gcc?

Comment 4 Fedora Update System 2021-03-06 21:20:21 UTC
FEDORA-2021-b9b2172321 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9b2172321

Comment 5 Fedora Update System 2021-03-07 18:45:44 UTC
FEDORA-2021-b9b2172321 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b9b2172321`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b9b2172321

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

Comment 6 Elliott Sales de Andrade 2021-03-08 10:15:05 UTC
I went back and looked at the logs, and your patch is broken. It depends on dwarf2.h, which I don't think is public, so the compile fails and decides that libbacktrace is unavailable. The package is now effectively a no-op, and all tests are skipped.

Comment 7 Ben Cotton 2022-05-12 16:25:03 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ben Cotton 2022-06-08 00:32:07 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.