From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: 30210@debbugs.gnu.org
Subject: bug#30210: pandoc not reproducible
Date: Tue, 23 Jan 2018 08:58:33 +0100 [thread overview]
Message-ID: <87po61ypjq.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87372x22c6.fsf@mdc-berlin.de>
The only file that differs is this:
/gnu/store/8ynsssfjjdjbawndmjlnjlqrh027rl9g-ghc-pandoc-1.17.2-check/lib/ghc-7.10.2/ghc-pandoc-1.17.2.conf.d/package.cache
/gnu/store/8ynsssfjjdjbawndmjlnjlqrh027rl9g-ghc-pandoc-1.17.2/lib/ghc-7.10.2/ghc-pandoc-1.17.2.conf.d/package.cache
I wonder if we should expect that other Haskell packages are also
affected by this.
--
Ricardo
next prev parent reply other threads:[~2018-01-23 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 18:09 bug#30210: pandoc not reproducible Ricardo Wurmus
2018-01-23 7:58 ` Ricardo Wurmus [this message]
2018-01-23 22:04 ` Ricardo Wurmus
2018-01-24 14:49 ` Ludovic Courtès
2019-02-04 14:03 ` Ricardo Wurmus
2021-09-13 1:41 ` Sarah Morgensen
2021-01-19 16:28 ` zimoun
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=87po61ypjq.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=30210@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 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).