From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>, bug-coreutils@gnu.org
Cc: guix-devel@gnu.org
Subject: LC_TIME category in Coreutils
Date: Mon, 23 Feb 2015 22:28:05 +0100 [thread overview]
Message-ID: <87vbis1foa.fsf_-_@gnu.org> (raw)
In-Reply-To: <871tlsgfnt.fsf@netris.org> (Mark H. Weaver's message of "Sat, 14 Feb 2015 19:52:06 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> I tried adding 'glibc-locales' to my system profile, and got this:
>
> ERROR: union-build: collision between file and directories ((files ("/gnu/store/nda1ih2iy8likfipl62afiqs6jwdsfxi-glibc-locales-2.20/share/locale/zh_CN/LC_TIME")) (dirs ("/gnu/store/mgfqcbm31rh738z13xlwh9ld9dm2vfvz-coreutils-8.23/share/locale/zh_CN/LC_TIME")))
>
> Indeed, in coreutils "share/locale/zh_CN/LC_TIME" is a directory
> containing a symbolic link "coreutils.mo" pointing to
> "../LC_MESSAGES/coreutils.mo", whereas in glibc-locales
> "share/locale/zh_CN/LC_TIME" is a binary file.
>
> Any ideas how to resolve this conflict?
I would have expected packages other than libc to provide only
LC_MESSAGES, so I didn’t think such collisions could happen.
This happens with Coreutils because its bootstrap.conf adds
‘EXTRA_LOCALE_CATEGORIES = LC_TIME’ to po/Makevars, and apparently
always has.
However, I suspect this isn’t needed. Can someone comment?
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-02-23 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 18:06 Locales not working Andreas Enge
2015-02-10 18:30 ` Andreas Enge
2015-02-11 20:39 ` Ludovic Courtès
2015-02-12 17:38 ` Andreas Enge
2015-02-15 0:52 ` Mark H Weaver
2015-02-23 21:28 ` Ludovic Courtès [this message]
2015-02-23 22:01 ` bug#19933: LC_TIME category in Coreutils Andreas Schwab
2015-02-24 23:07 ` Ludovic Courtès
2015-02-23 22:15 ` bug#19933: " Paul Eggert
2015-02-24 23:01 ` Ludovic Courtès
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=87vbis1foa.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=bug-coreutils@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.