From: Florian Weimer <fw@deneb.enyo.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Eryu Guan <guaneryu@gmail.com>, Paul Smith <psmith@gnu.org>,
Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, bug-make@gnu.org,
Jim Meyering <meyering@fb.com>
Subject: Re: xfstests can't be installed by running make install
Date: Wed, 18 Jul 2018 08:26:15 +0200 [thread overview]
Message-ID: <87601dgiuw.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20180717225801.GA19934@dastard> (Dave Chinner's message of "Wed, 18 Jul 2018 08:58:01 +1000")
* Dave Chinner:
(The regular expression or glob pattern [a-z] matches B.)
>> This is ultimately caused by a locale data update which was backported
>> into Fedora 28 (glibc 2.27) and its derivatives. Upstream glibc only
>> has this change for version 2.28 (not yet released). It's currently
>> not considered a release blocker, if it's even considered a bug at
>> all.
>
> So what you are saying (i.e. "not a bug") is that we should expect
> widespread regex breakage in custom scripts when distros roll out
> glibc 2.28 because it will break assumptions people have coded into
> their scripts and custom code for the past 20+ years?
According to POSIX, [a-z] is undefined in locales other than C or
POSIX. This isn't a recent change. POSIX pretty much says that you
need to use [[:lower:]] instead.
I don't doubt that a lot of code doesn't follow these rules, and
saying that it is broken according to POSIX doesn't help users who run
into issues. But on the glibc side, I don't see anyone else arguing
that this needs to be fixed in glibc.
next prev parent reply other threads:[~2018-07-18 7:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:33 xfstests can't be installed by running make install Zorro Lang
2018-07-11 16:39 ` Eryu Guan
2018-07-11 16:54 ` Zorro Lang
2018-07-15 5:43 ` Dave Chinner
2018-07-15 7:11 ` Eryu Guan
2018-07-16 7:30 ` Zorro Lang
2018-07-16 11:48 ` Paul Smith
2018-07-17 3:32 ` Eryu Guan
2018-07-17 20:15 ` Florian Weimer
2018-07-17 22:58 ` Dave Chinner
2018-07-18 6:26 ` Florian Weimer [this message]
2018-07-18 3:15 ` Zorro Lang
2018-07-18 3:47 ` Zorro Lang
2018-07-18 4:05 ` Zorro Lang
2018-07-18 6:04 ` Florian Weimer
2018-07-18 8:31 ` Zorro Lang
2018-07-18 8:47 ` Florian Weimer
2018-07-18 10:12 ` Zorro Lang
2018-07-18 10:19 ` Zorro Lang
2018-07-19 16:21 ` Florian Weimer
2018-07-20 2:12 ` Zorro Lang
2018-07-18 10:56 ` spagoveanu
2018-07-17 5:24 ` Dave Chinner
2018-07-17 5:57 ` Zorro Lang
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=87601dgiuw.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=bug-make@gnu.org \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=meyering@fb.com \
--cc=psmith@gnu.org \
--cc=zlang@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.