From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29978] fedabipkgdiff --self-compare -a --from fc37 evolution-data-server-tests has problems
Date: Mon, 09 Jan 2023 20:00:55 +0000 [thread overview]
Message-ID: <bug-29978-9487-mmkctXMnTd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29978-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29978
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
running through all the commands emitted by
$ fedabipkgdiff --self-compare --dry-run -a --from fc37
evolution-data-server-tests
They seem to assert inconsistently but reliably when run from fedabipkgdiff.
However, the other problem with the data inconsistency or proper escaping may
be related.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-09 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 19:45 [Bug default/29978] New: " woodard at redhat dot com
2023-01-09 20:00 ` woodard at redhat dot com [this message]
2023-01-09 20:02 ` [Bug default/29978] " woodard at redhat dot com
2023-01-09 20:13 ` woodard at redhat dot com
2023-03-10 18:53 ` dodji 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-29978-9487-mmkctXMnTd@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).