From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: 27554-done@debbugs.gnu.org
Subject: bug#27554: Add dirvish and dependencies
Date: Thu, 19 Oct 2017 01:16:24 +0200 [thread overview]
Message-ID: <87tvyw2gjb.fsf@elephly.net> (raw)
In-Reply-To: <20170702153847.GA18347@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Sun, Jul 02, 2017 at 05:20:37PM +0200, Ludovic Courtès wrote:
>> Hi Chris!
>>
>> Christopher Allan Webber <cwebber@dustycloud.org> skribis:
>>
>> > From 60a448f1daf37927155577dabaf1c090f9404bee Mon Sep 17 00:00:00 2001
>> > From: Christopher Allan Webber <cwebber@dustycloud.org>
>> > Date: Sat, 1 Jul 2017 20:45:04 -0500
>> > Subject: [PATCH 1/3] gnu: Add perl-libtime-parsedate.
>> >
>> > * gnu/packages/perl.scm (perl-libtime-parsedate): New variable.
>>
>> [...]
>>
>> > + (arguments
>> > + ;; Output when running tests:
>> > + ;; t/metdate.t ... skipped: It seems localtime() does not honor
>> > + ;; $ENV{TZ} when set in the test script.
>> > + ;; Seemingly related:
>> > + ;; https://stackoverflow.com/questions/19956693/timeparsedate-install-fail
>> > + ;; https://rt.cpan.org/Public/Bug/Display.html?id=90367
>> > + `(#:tests? #f))
>>
>> Perhaps if we add a dependency on tzdata and set TZDIR, as is done for
>> ‘duplicity’ for instance, the tests would run?
>>
>> Anyway this probably shouldn’t block the whole series!
>
> If it only uses them for tests, please use the special tzdata package
> that is just for tests, currently tzdata-2017a.
Thanks for the hint.
I’ve implemented the suggested changes and pushed these patches to
master with commit 0ff4425ce.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-10-18 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 1:57 [bug#27554] Add dirvish and dependencies Christopher Allan Webber
2017-07-02 15:20 ` Ludovic Courtès
2017-07-02 15:38 ` Leo Famulari
2017-10-18 23:16 ` Ricardo Wurmus [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=87tvyw2gjb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=27554-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.