!LemuOOvbWqRXodtSsw:nixos.org

NixOS Reproducible Builds

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

Load older messages


SenderMessageTime
22 Apr 2026
@manueljacob:matrix.orgmanueljacobE.g., when making a change to binutils, how can I check whether it broke reproducibility of some package?15:12:12
@raboof:matrix.orgraboofInteresting question. I don't think we have an easy answer because we don't even have a full definition of "the same package" across changes, nor of "binutils and its dependendees" ;) . But doing a reproduciblity report for 'binutils and its referrers in nixpkgs' for two sets and comparing the results probably should get you close. Might be neat to set up a local instance of https://github.com/nix-community/lila for the reporting. expect a bit of a project, though. this would be valuable to document once you figure it out though!15:31:15
@manueljacob:matrix.orgmanueljacobWell, that would probably build 10s of thousands of packages. What would be a suitable set of packages to build?15:55:01
@manueljacob:matrix.orgmanueljacobIdeally, the re-build with changed binutils should rebuild only packages that were shown to be reproducible.15:55:37
@manueljacob:matrix.orgmanueljacob(shown to be reproducible before the binutils change)15:58:30
@raboof:matrix.orgraboofThat's ideally still most of them though 😊. I like to take 'the graphical installation iso' as testset (and that should be easy enough to prune to only things that depended on binutils), but that's still pretty arbitrary. Maybe nixpkgs-small? (not sure what's in that)16:21:55
@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

Show newer messages


Back to Room ListRoom Version: 6