From: "sourceware at nerdbynature dot de" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24046] en_US locale doesn't define date_fmt
Date: Thu, 12 Mar 2020 02:37:20 +0000 [thread overview]
Message-ID: <bug-24046-716-AmZkYVMCTd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24046-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24046
CK <sourceware at nerdbynature dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sourceware at nerdbynature dot de
--- Comment #8 from CK <sourceware at nerdbynature dot de> ---
Hm, is this really fixed? Even with glibc 2.29 and newer I have trouble getting
a 24 hour time output:
==========================================================
$ /lib/x86_64-linux-gnu/libc.so.6 | head -1
GNU C Library (Debian GLIBC 2.29-10) stable release version 2.29.
$ export LC_TIME=C
$ date; date +%c; date +%X
Wed 11 Mar 2020 07:01:50 PM PDT
Wed 11 Mar 2020 07:01:50 PM PDT
07:01:50 PM
==========================================================
Setting "LC_TIME" to different values (en_GB, de_DE) doesn't help, although the
locale definitions would be available:
==========================================================
$ strace -e openat -f date
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
Wed 11 Mar 2020 07:09:08 PM PDT
+++ exited with 0 +++
$ strings /usr/lib/locale/locale-archive | grep en_GB
en_GB.iso88591
en_GB
en_GB.utf8
en_GB.iso885915
==========================================================
Same result when setting every other LC_* variable to "C" or "en_GB" -- only
LC_ALL=en_GB did the trick. The same for two other systems, both running glibc
2.30. Only some glibc 2.31 system appears to do The Right Thing:
==========================================================
$ LC_TIME=C date
Wed Mar 11 18:46:37 PDT 2020
$ LC_TIME=en_US date
Wed 11 Mar 2020 06:46:48 PM PDT
$ LC_TIME=en_GB date
Wed Mar 11 18:46:54 PDT 2020
==========================================================
Could this be related to commit 75ba929987 ("Multiple locales: Add date_fmt
(bug 24054)") perhaps?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-03-12 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 23:39 [Bug localedata/24046] New: " aurelien at aurel32 dot net
2019-01-02 12:20 ` [Bug localedata/24046] " fweimer at redhat dot com
2019-01-07 13:58 ` cvs-commit at gcc dot gnu.org
2019-01-07 14:01 ` aurelien at aurel32 dot net
2019-01-31 17:17 ` cvs-commit at gcc dot gnu.org
2019-03-29 22:19 ` dilfridge at gentoo dot org
2019-03-29 22:52 ` aurelien at aurel32 dot net
2019-04-02 20:33 ` cloos at jhcloos dot com
2019-04-02 20:58 ` schwab@linux-m68k.org
2020-03-12 2:37 ` sourceware at nerdbynature dot de [this message]
2020-03-12 9:09 ` schwab@linux-m68k.org
2020-05-05 13:57 ` carlos 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-24046-716-AmZkYVMCTd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).