RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1951501 - Error encountered while running fedabipkgdiff (against binutils)
Summary: Error encountered while running fedabipkgdiff (against binutils)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libabigail
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Dodji Seketeli
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-20 09:47 UTC by Martin Cermak
Modified: 2022-11-01 07:29 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-01 07:29:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Cermak 2021-04-20 09:47:46 UTC 
Reproducible with libabigail-1.8.2-1.el9 and currentl upstream version libabigail/b215a2115376225b04b4d6b25acc6c5a1b4021e9:



2021-04-19 01:21:54.714218 Running '/mnt/tests/tools/libabigail/Sanity/selfcheck/fedabipkgdiff --abipkgdiff /usr/bin/abipkgdiff --server https://brewhub.engineering.redhat.com/brewhub --topurl http://download.devel.redhat.com/brewroot --self-compare -a --from el9 binutils'

2021-04-19 01:27:30.483071 Error encountered while running fedabipkgdiff with error message: 
 /root/.cache/libabigail/abipkgdiff-tmp-dir-VeMQh3/package1/abixml/usr/bin/ld.abi:46124: parser error : Unescaped '<' not allowed in attributes values
      <enum-decl name='__anonymous_enum__' is-anonymous='yes' linkage-name='<ano
                                                                            ^
/root/.cache/libabigail/abipkgdiff-tmp-dir-VeMQh3/package1/abixml/usr/bin/ld.abi:46124: parser error : attributes construct error
      <enum-decl name='__anonymous_enum__' is-anonymous='yes' linkage-name='<ano
                                                                            ^
/root/.cache/libabigail/abipkgdiff-tmp-dir-VeMQh3/package1/abixml/usr/bin/ld.abi:46124: parser error : Couldn't find end of Start Tag enum-decl
      <enum-decl name='__anonymous_enum__' is-anonymous='yes' linkage-name='<ano
                                                                            ^
Comment 1 Dodji Seketeli 2021-09-08 14:43:33 UTC 
This should now be fixed by upstream commits

from: https://sourceware.org/git?p=libabigail.git;a=commit;h=4e029df894e05c76aec34afb646c9fa019955b35
to: https://sourceware.org/git?p=libabigail.git;a=commit;h=c808263635804bdd271fd889c93e7e3a36695678

The fixes should be available in the coming libabigail 2.0 release.
Comment 3 Michal Kolar 2022-09-25 22:31:42 UTC 
Tested with 7060a0b upstream commit
Comment 5 RHEL Program Management 2022-11-01 07:29:04 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.