| 6 Oct 2021 |
 ryantm | Possibly, I don't really know, I'm not the maintainer of this. | 15:01:02 |
 Alyssa Ross | that's probably what I'd do, if possible | 15:01:33 |
 tomberek | or there's a way to tell git to not do that | 15:01:49 |
| Alyssa Ross | tomberek: well no, because it happens at tarball generation time, and github generates the tarballs | 15:02:18 |
| Alyssa Ross | that's why doing fetchgit ourselves would fix it | 15:02:22 |
| tomberek | this would be one of those cases for non-deterministic derivations,,, fetch impurely, clean up the impurity, then FOD to bring it back into the pure world. https://github.com/FRidh/nix/commit/9fc59606bac1f6f3e6e6d7a9f02b58a7df5762ed | 15:03:57 |
| Alyssa Ross | oh actually we probably can do that with what we have | 15:04:37 |
| Alyssa Ross | we can already do that in a single derivation | 15:05:00 |
| Alyssa Ross | ryantm: can we just delete that file in fetchFromGitHub's postFetch? | 15:05:01 |
 j-k | adding the wasm evaluation feature to open-policy-agent breaks reproducability. I have no idea what I'm looking at here: | 16:11:17 |
| j-k | 
Download image.png | 16:11:21 |
| j-k | Looks like this article might help actually https://blog.filippo.io/reproducing-go-binaries-byte-by-byte/ | 16:12:41 |
|  dotlambda joined the room. | 16:20:21 |
| dotlambda | In reply to @qyliss:fairydust.space
ryantm: can we just delete that file in fetchFromGitHub's postFetch? I think we should, but do you mean for this package only or for fetchFromGithub in general? | 16:24:51 |
| Alyssa Ross | I mean for this package | 16:25:04 |
| Alyssa Ross | not the gitattributes file, that wouldn't help | 16:25:11 |
| Alyssa Ross | the one that it's doing export-subst on | 16:25:18 |
| dotlambda | And you don't think it's worth always checking for that line in .gitattributes and deleting the respective files | 16:28:05 |
| dotlambda | * And you don't think it's worth always checking for that line in `.gitattributes` and deleting the respective files? | 16:28:11 |
| Alyssa Ross | no, I don't think that's a good idea | 17:30:25 |
| Alyssa Ross | it would break existing hashes, and also be very confusing -- what if you have a 10000 line main.c file that's export-subst? | 17:30:48 |
| Alyssa Ross | one thing we could do would be to scan for export-subst and just fail the fetcher if it was found | 17:31:22 |
| Alyssa Ross | with a nice explanatory error message saying to either: · use a static release tarball; · use fetchgit; · carefully adjust the tarball, and then sed the export-subst line out of .gitattributes | 17:32:32 |
| 7 Oct 2021 |
 baloo | https://github.com/NixOS/nixpkgs/pull/140868 back to 100% tomorrow? | 19:43:48 |
 @rick:matrix.ciphernetics.nl | Would be nice :) | 19:46:32 |
| @rick:matrix.ciphernetics.nl | Saw that the gnome_iso wasn't updated for a while either | 19:46:47 |
| baloo | Yeah but this is a different issue | 20:47:26 |
| baloo | The builders are running out of disk space | 20:47:41 |
| tomberek | I'll run mine: https://buildkite.com/tomberek/r13y/builds/22 | 20:47:59 |
 @trofi:matrix.org | is there an easy way to make all local builds to check for reproducibility? (I'd like to check every package my system uses). I tried specifying --repeat 1 and did not notice any effect. Example command:
$ nix-build -E 'with import <nixpkgs> {}; builtins.derivation { name = "flaky-foo"; builder = "${bash}/bin/bash"; args = [ "-c" "${coreutils}/bin/date +%N > $out" ]; system = builtins.currentSystem; }' --repeat 10
| 20:52:46 |
