unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Sarah Morgensen <iskarian@mgsn.dev>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 30210-done@debbugs.gnu.org
Subject: bug#30210: pandoc not reproducible
Date: Sun, 12 Sep 2021 18:41:32 -0700	[thread overview]
Message-ID: <86tuipjlpv.fsf@mgsn.dev> (raw)
In-Reply-To: <87h8djhcrb.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 04 Feb 2019 15:03:20 +0100 (2 years, 31 weeks, 3 days ago)")

Hello,

Ricardo Wurmus <rekado@elephly.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>>
>>>> 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
>>>
>>> At least they seem to contain the same strings albeit in a different
>>> order.  “diff <(strings a|sort) <(strings b|sort)” shows no
>>> differences.  (Of course there could be other differences than order,
>>> which simply don’t appear to be strings.)
>>
>> That sounds like code using readdir(2) and not sorting the returned
>> entries, as was the case for gtk-update-icon-cache or whatever it’s
>> called.
>
> This package.cache problem has been fixed with commit
> 5de93cdba77db3777f8f026c029acadd7b8bdde3.
>
> Unfortunately it is now bin/pandoc that differs across builds.
>
> --
> Ricardo

I found this old bug.  I tested both pandoc and ghc-pandoc and it looks
like this is no longer an issue (perhaps fixed partially in #43834), so
I'm closing.  Please reopen otherwise.

Thanks,
--
Sarah




  reply	other threads:[~2021-09-13  1:42 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
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 [this message]
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=86tuipjlpv.fsf@mgsn.dev \
    --to=iskarian@mgsn.dev \
    --cc=30210-done@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).