News for hackers. Stuff that matters.
Re:“Packages should be reproducible” added to Debian Policy by agumonkey on Monday August 14, 2017 @04:06PM (#15012331)
I had this reflex, but IIRC the reproducible build effort does a few things differently (and some more) than nix. I can't recall which, but there were meaningful differences.
Re:“Packages should be reproducible” added to Debian Policy by joepie91_ on Monday August 14, 2017 @07:06PM (#15013831)
The short version is that they're different kinds of reproducibility.

The reproducibility that this post is about is for auditability ("verify that the binary originated from the claimed source"), whereas the reproducibility in Nix is for reliability ("ensure that the same package either fails or succeeds on every system in the exact same way, regardless of what the environment looks like").

Both are nice to have, but they are only tangentially related.

Re:“Packages should be reproducible” added to Debian Policy by mbrock on Tuesday August 15, 2017 @12:44AM (#15015576)
Nix does not particularly care about the hash of the result of a build, but mostly only the hash of the input.

When you download a package from the binary cache of Nix, you use the input hash. The binary cache contents may differ depending on the system of the build server.

Nix does try to eliminate nondeterminism in their builds though.