From: ludo@gnu.org (Ludovic Courtès)
To: alex.sassmannshausen@gmail.com
Cc: "bug-guix@gnu.org" <bug-guix@gnu.org>
Subject: Re: Timezone problems
Date: Thu, 09 May 2013 22:41:18 +0200 [thread overview]
Message-ID: <87obcjvqc1.fsf@gnu.org> (raw)
In-Reply-To: <87mws4o8ex.fsf@damselfly.home> (Alex Sassmannshausen's message of "Thu, 09 May 2013 08:37:58 +0000")
Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
> I'm running into issues whereby the 'date' command that is part of the
> coreutils package (installed through guix) returns non-timezone
> corrected values (i.e. it returns UTC even for local time).
Actually you first need to install the ‘tzdata’ package (which I just
added yesterday!). Then you must set the TZDIR environment variable to
point to it, like this:
export TZDIR=$HOME/.guix-profile/share/zoneinfo
The C library (the one from Guix) will then get timezone info from there.
> I suspect this was to do with the locale complications of the earlier
> gcc version that was part of guix, and that locale issue seems to be
> resolved now: Guile 2.0.9 compiled with the new gcc does not complain
> about locale settings anymore.
This is actually unrelated but yes, this one’s fixed too.
> Would guix normally have recompiled coreutils following the gcc upgrade
> too? If so then the problem must be something else — but the date
> program invoked through /bin/date returns the correct local time (installed
> through aptitude), so it seems guix specific.
>
> If not — is there a way to force re-installation from scratch for just
> coreutils?
What matters most is what’s in your profile. I just run ‘guix package --upgrade’,
which atomically upgrades everything that’s installed in your profile
(so you get the new Coreutils, and everything linked against the new libc.)
HTH!
Ludo’.
next prev parent reply other threads:[~2013-05-09 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 8:37 Timezone problems Alex Sassmannshausen
2013-05-09 20:41 ` Ludovic Courtès [this message]
2013-05-14 21:06 ` Alex Sassmannshausen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obcjvqc1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alex.sassmannshausen@gmail.com \
--cc=bug-guix@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).