!LemuOOvbWqRXodtSsw:nixos.org

NixOS Reproducible Builds

555 Members
Report: https://reproducible.nixos.org Project progress: https://github.com/orgs/NixOS/projects/30128 Servers

Load older messages


SenderMessageTime
22 Apr 2026
@gkleen:synapse.li@gkleen:synapse.li left the room.20:36:17
26 Apr 2026
@manueljacob:matrix.orgmanueljacob I think what I’ll do is to execute nix-build --check for every derivation in the build closure of some package, before and after the change, and compare them (filtering uninteresting ones such as those common between the two closures). 12:51:26
@manueljacob:matrix.orgmanueljacob Mostly unrelated: I found that the coreutils package is not reproducible if built on different days. Would it make sense to catch such things by Lila? 12:55:58
@julienmalka:matrix.orgJulienSupposedly that's the kind of thing we catch because not everyone rebuilds on the same day ?19:20:17
@manueljacob:matrix.orgmanueljacobWell, https://reproducibility.nixos.social/evaluations/1/e4bae1bd10c9 and https://reproducibility.nixos.social/evaluations/4/e4bae1bd10c9 didn’t catch it.19:33:49
@manueljacob:matrix.orgmanueljacobOr does it not check not the debug packages?19:34:33
@manueljacob:matrix.orgmanueljacob * 19:51:52
@julienmalka:matrix.orgJulienIt depends what is in the minimal iso19:55:50
@manueljacob:matrix.orgmanueljacobSure, it doesn’t make much sense for the minimal-iso-runtime jobset to check reproducibility of anything not included in the minimal ISO, and I assume that debug information is not included in the ISO. I’m not sure it makes sense for minimal-iso-build-closure, but I think it would be useful to have all outputs (including debug information) checked for some packages in some jobset.20:35:43
27 Apr 2026
@ninja:worldethicaldataforum.orgNinja joined the room.14:39:15
28 Apr 2026
@aangularframework:matrix.orgAangularity joined the room.04:39:25
@implr:hackerspace.plimplr joined the room.08:13:50
@implr:hackerspace.plimplrHi, I wrote in #users earlier but it got buried under a different discussion. I have a coreutils build failing tests, but only under nix on Gentoo. On nixos it builds fine. The kernel is of course different, but that shouldn't affect that test as far as I can tell08:18:45
@implr:hackerspace.plimplr it's nix-build -E '(import <nixpkgs> {}).pkgs.coreutils.override { singleBinary = false; }' (with the channel pointing to the same commit, but it doesn't seem to matter anyway, old versions still fail) 08:18:56
@implr:hackerspace.plimplr curiously, on Gentoo nix-shell <derivation>; genericBuild; checkPhase also passes, so idk how do i even debug this 08:19:54
29 Apr 2026
@implr:hackerspace.plimplrfor posterity, this is an issue with how the gentoo packaging of nix builds its sandbox busybox: https://github.com/trofi/nix-guix-gentoo/blob/master/sys-apps/busybox-nix-sandbox-shell/busybox-nix-sandbox-shell-1.36.1.ebuild#L105 is different from the nixos one21:37:26
30 Apr 2026
@raboof:matrix.orgraboofOh wow. Good find06:23:07
@isabel:isabelroses.comisabel changed their profile picture.18:45:59
19 May 2021
@grahamc:nixos.org@grahamc:nixos.org set the history visibility to "world_readable".16:14:09
@qyliss:fairydust.spaceAlyssa Ross joined the room.16:14:59
@baloo_:matrix.orgbaloo joined the room.16:15:12
@baloo_:matrix.orgbaloo 16:15:29
@grahamc:nixos.org@grahamc:nixos.orgchanged room power levels.16:21:56
@grahamc:nixos.org@grahamc:nixos.orgchanged room power levels.16:22:02
@immae:matrix.orgimmae joined the room.16:23:59
@sumner:sumnerevans.comsumner joined the room.16:35:41
@raboof:matrix.orgraboof joined the room.16:41:20
@grahamc:nixos.org@grahamc:nixos.org 16:42:10
@ninjatrappeur:matrix.orgNinjaTrappeur joined the room.16:42:24
@rgrunbla:matrix.orgReventlov joined the room.16:46:08

Show newer messages


Back to Room ListRoom Version: 6