bug#30210: pandoc not reproducible

[Sarah Morgensen]

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