From: "bochecha at daitauha dot fr" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/23533] New: abidiff is confused when an "=" sign is used in a suppression label
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <bug-23533-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23533
Bug ID: 23533
Summary: abidiff is confused when an "=" sign is used in a
suppression label
Product: libabigail
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: bochecha at daitauha dot fr
CC: libabigail at sourceware dot org
Target Milestone: ---
Because of https://sourceware.org/bugzilla/show_bug.cgi?id=23492, I have to
ignore libgfortran, so I used the following suppression file:
[suppress_file]
# https://sourceware.org/bugzilla/show_bug.cgi?id=23492
label = Libabigail can't handle libgfortran.so
file_name_regexp = libgfortran\\.so.*
This works just fine.
However, if I put the bug URL in the label, as I originally wanted to, then
abidiff will skip the suppression rule, and NOT ignore the file.
I found that this is due to the "=" sign in the bug URL, which seems to confuse
the INI parser somehow. It probably can't correctly parse the key/value.
I tried quoting the string, but that didn't change anything, those all lead to
the same behaviour:
label = https://sourceware.org/bugzilla/show_bug.cgi?id=23492
label = 'https://sourceware.org/bugzilla/show_bug.cgi?id=23492'
label = "https://sourceware.org/bugzilla/show_bug.cgi?id=23492"
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-08-16 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 0:00 bochecha at daitauha dot fr [this message]
2018-01-01 0:00 ` [Bug default/23533] " dodji at redhat dot com
2018-01-01 0:00 ` 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-23533-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).