bug#30210: pandoc not reproducible

bug#30210: pandoc not reproducible

[Ricardo Wurmus]

The ghc-pandoc package for version 1.17.2 cannot be built reproducibly.

bug#30210: pandoc not reproducible

[Ricardo Wurmus]

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

bug#30210: pandoc not reproducible

[Ricardo Wurmus]

> 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.)

> I wonder if we should expect that other Haskell packages are also
> affected by this.

Other packages also have a “package.cache”, but I don’t think they are
used.  The build system creates a new temporary “package.cache” file for
all Haskell packages, and we have a profile hook that creates such a
file for when Haskell packages are installed to profiles.

Could we maybe just delete “package.cache” after the installation phase?

(Even if we can make our packages appear to be deterministic, will they
really be?  This GHC bug sounds bad for us:
https://ghc.haskell.org/trac/ghc/ticket/4012)

--
Ricardo

bug#30210: pandoc not reproducible

[Ludovic Courtès]

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.

Ludo’.

bug#30210: pandoc not reproducible

[Ricardo Wurmus]

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

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

bug#30210: pandoc not reproducible

[zimoun]

Hi Ricardo,


On Mon, 22 Jan 2018 at 19:09, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> wrote:
> The ghc-pandoc package for version 1.17.2 cannot be built reproducibly.

On my machine, with Guix cb68ae6, the usual:

  guix build pandoc –no-grafts
  guix build pandoc –no-grafts –check

does not report a reproducibility issue.  Idem with ghc-pandoc.

Since, Pandoc is at 2.7.3 and without the parallel Haskell build system,
it should be reproducible, I guess.

Could you confirm?  If ok for you, this bug report could be close.


All the best,
simon