all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: 39665@debbugs.gnu.org
Subject: bug#39665: r-readr in a container has got no timezone data
Date: Thu, 20 Feb 2020 13:44:29 +0100	[thread overview]
Message-ID: <CAJ3okZ0N6EfGx+KA9EZRJJMkQHxPMi90RmDNroDvO_O_dUvuLg@mail.gmail.com> (raw)
In-Reply-To: <20200218151926.2yhah6zc7pym2fiu@wzguix>

Dear,

On Tue, 18 Feb 2020 at 16:21, Wiktor Żelazny <wz@freeshell.de> wrote:
>
> Related to [1]. Reproducing:
>
>    guix environment -C --pure --ad-hoc r r-readr
>    Rscript -e 'library(readr); default_locale()'

The output is:

--8<---------------cut here---------------start------------->8---
Error: Unknown TZ UTC
In addition: Warning message:
In OlsonNames() : no Olson database found
Execution halted
sh: rm: command not found
--8<---------------cut here---------------end--------------->8---


> (actually, one needs also coreutils and grep to do that, but that’s
> beyond the point). I haven’t tried it (yet?), but maybe it suffices to
> add tzdata to r-readr inputs in the package definition to fix this
> issue.

Just adding tzdata to the propgapated-inputs list is not enough.


Well, I do not understand why the test suite pass. It should fail if
locale date is required... I am missing a point. Especially when
reading these 2 comments:

https://github.com/tidyverse/readr/issues/952#issuecomment-451244171
https://github.com/tidyverse/readr/issues/952#issuecomment-451255375

Let investigate more...


Thank you for the report.
All the best,
simon

      reply	other threads:[~2020-02-20 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 15:19 bug#39665: r-readr in a container has got no timezone data Wiktor Żelazny
2020-02-20 12:44 ` zimoun [this message]

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=CAJ3okZ0N6EfGx+KA9EZRJJMkQHxPMi90RmDNroDvO_O_dUvuLg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=39665@debbugs.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 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.