public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29406] New: 389-ds-base-2.1.3-1.fc36.armv7hl.rpm fails self-compare
Date: Mon, 25 Jul 2022 21:36:35 +0000	[thread overview]
Message-ID: <bug-29406-9487@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29406

            Bug ID: 29406
           Summary: 389-ds-base-2.1.3-1.fc36.armv7hl.rpm fails
                    self-compare
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: woodard at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

This is with the latest trunk as of: df28c220976f41620b0bd7b22000815e11f66b75

When doing:
$ fedabipkgdiff --self-compare -a --from fc36 389-ds-base

You get an error:

Comparing the ABI of binaries between 389-ds-base-2.1.3-1.fc36.armv7hl.rpm and
389-ds-base-2.1.3-1.fc36.armv7hl.rpm:

==== SELF CHECK SUCCEEDED for 'libpwdchan-plugin.so' ====
==== SELF CHECK SUCCEEDED for 'libentryuuid-syntax-plugin.so' ====
==== SELF CHECK SUCCEEDED for 'libentryuuid-plugin.so' ====
======== comparing'libback-ldbm.so' to itself wrongly yielded result:
===========
  Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added
function
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'libback-ldbm.so'

This is platform specfic to armv7hl, all the other architectures compare
correctly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-25 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 21:36 woodard at redhat dot com [this message]
2022-07-26 18:52 ` [Bug default/29406] " woodard at redhat dot com
2022-07-26 20:04 ` woodard at redhat dot com
2022-10-14 16:05 ` woodard at redhat dot com

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-29406-9487@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).