From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27267] Assertion comparing ABIs on rawhide
Date: Thu, 04 Feb 2021 10:43:05 +0000 [thread overview]
Message-ID: <bug-27267-9487-xLhcBEmB0z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27267-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27267
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from dodji at redhat dot com ---
(In reply to dodji from comment #5)
> Okay, I could finally reproduce the Rawhide issue. Thanks for the hand
> holding. It seems to look different from the Fedora 33 one.
>
> At least the Rawhide one should now be fixed by commit
> https://sourceware.org/git/?p=libabigail.git;a=commit;
> h=e5c7fd34007daec012810601efc3481bb5823750 recently applied to the mainline
> branch.
>
> It should be available in libabigail 2.0 or maybe in an intermediate 1.8.2
> release before that.
>
> I'll be trying to reproduce the Fedora 33 one now.
I have just tested that patch in the context of Fedora 33 as well, the CI
pipeline seems to work with it.
I am thus closing this problem report as the issue seems to be fixed. It
should percolate into a package update near you soon.
Thanks your taking the time to report the issue and sorry for the
inconvenience.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-02-04 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 14:40 [Bug default/27267] New: " bugzilla at hadess dot net
2021-01-28 15:28 ` [Bug default/27267] " dodji at redhat dot com
2021-01-28 15:49 ` bugzilla at hadess dot net
2021-02-01 13:49 ` dodji at redhat dot com
2021-02-01 14:14 ` bugzilla at hadess dot net
2021-02-04 10:00 ` dodji at redhat dot com
2021-02-04 10:43 ` dodji at redhat dot com [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27267-9487-xLhcBEmB0z@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).