| 17 May 2023 |
 delroth | and that would explain why I'm not seeing that build-id difference when diffing guix's NARs, they might not have that randomized out-of-tree build output path in their derivations | 15:46:49 |
| delroth | (I expect that sourceRoot is fixed for them as it is for Nix, but not completely sure of that) | 15:47:16 |
| delroth | https://github.com/NixOS/nixpkgs/commit/d75cff2ee3bb6d91c818d43d1ba7603bb6dacd59 | 16:09:14 |
| delroth | I'll send a PR to make it a fixed path, in the meantime I also remembered that my sandbox troubles only impacted uid mapping not chrooting, so I'm now fairly convinced that it's a regression from that commit adding randomness | 16:10:53 |
| delroth | If someone wants to test and/or snipe this feel free, won't be available for the next 6h | 16:11:23 |
| 19 May 2023 |
|  @jackleightcap:matrix.org joined the room. | 18:40:13 |
| 20 May 2023 |
| delroth | iso minimal (runtime) run on latest staging: https://delroth.net/report-iso_minimal/ | 03:18:24 |
| delroth | linux is finally fixed, down to just python | 03:18:31 |
 baloo | what's about the unchecked paths? | 05:10:18 |
| baloo | about python: https://github.com/python/cpython/issues/92132 | 05:12:20 |
| delroth | I'm not sure why that systemd path is marked as unchecked but I don't think I've seen any repro issues in the past with it, so probably just a random issue with my build | 05:33:56 |
| delroth | and yeah, I'm doing a build now with python 3.11 as default to confirm | 05:34:18 |
| delroth | only slightly related but I wonder if we really need Python in the minimal ISO... it's used by a few ZFS user scripts that are probably seldom used and definitely not needed for mounting/recovery (e.g. arc_summary), it's used by smb2-quota (similar story), and the rest seems to all be derivations that have Python bindings in their main output when it could be a separate output | 05:56:45 |
| delroth | minimal ISO built with Python 3.11: "521 out of 521 (100.00%) paths in the nixos.iso_minimal.x86_64-linux build closure are reproducible! 0 paths remained unchecked" | 07:15:46 |
|  raphi joined the room. | 09:29:35 |
 @rnhmjoj:maxwell.ydns.eu | In reply to @delroth:delroth.net
only slightly related but I wonder if we really need Python in the minimal ISO... it's used by a few ZFS user scripts that are probably seldom used and definitely not needed for mounting/recovery (e.g. arc_summary), it's used by smb2-quota (similar story), and the rest seems to all be derivations that have Python bindings in their main output when it could be a separate output python is needed for the systed-boot install script, so you're probably going to fetch it anyway | 10:23:33 |
| @rnhmjoj:maxwell.ydns.eu | * python is needed for the systemd-boot install script, so you're probably going to fetch it anyway | 16:53:59 |
 raitobezarius | but soon we can remove it | 17:02:11 |
| raitobezarius | once we refactor the bootloader installation story | 17:02:29 |
| @rnhmjoj:maxwell.ydns.eu | what are you rewriting it into? I hope not perl | 18:37:49 |
| raitobezarius | https://github.com/nix-community/lanzaboote/tree/master/rust/tool/src | 18:38:16 |
| @rnhmjoj:maxwell.ydns.eu | how is rust in terms of reproducibility? | 18:42:33 |
| raitobezarius | binary repro? | 18:42:42 |
| @rnhmjoj:maxwell.ydns.eu | yes | 18:42:53 |
| raitobezarius | https://github.com/rust-lang/rust/issues/34902 | 18:43:12 |
| @rnhmjoj:maxwell.ydns.eu | tl;dr? | 18:45:12 |
| raitobezarius | they are committed to it, but sometimes it breaks | 18:45:20 |
 @ulli:hrnz.li | (rustc does not reproduce in nixpkgs) | 18:45:58 |
| @rnhmjoj:maxwell.ydns.eu | rustc itself or rustc-generated binaries? | 18:46:01 |
| raitobezarius | this is about rustc-generated binaries | 18:46:12 |
