!LemuOOvbWqRXodtSsw:nixos.org

NixOS Reproducible Builds

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

Load older messages


SenderMessageTime
6 Jan 2025
@emilazy:matrix.orgemily "You can try the new experimental -fobject-determinism flag to enable deterministic object code generation." https://blog.haskell.org/ghc-9-12-cabal-3-14/ 👀 23:24:56
7 Jan 2025
@drupol:matrix.orgPolhttps://salsa.debian.org/reproducible-builds/reproducible-website/-/commit/1179e9457bf7280f1954a33b6505cc6bdff3344207:47:41
@drupol:matrix.orgPolThanks for the heads up07:47:50
@sigmasquadron:matrix.orgFernando Rodrigues changed their display name from SigmaSquadron to SigmaSquadron (Away until 2024-01-12).19:35:57
9 Jan 2025
@drupol:matrix.orgPolIt is published: https://reproducible-builds.org/reports/2024-12/#other-development-news12:13:55
10 Jan 2025
@sigmasquadron:matrix.orgFernando Rodrigues changed their display name from SigmaSquadron (Away until 2024-01-12) to SigmaSquadron (Away until 2024-01-11).22:15:46
@sigmasquadron:matrix.orgFernando Rodrigues changed their display name from SigmaSquadron (Away until 2024-01-11) to SigmaSquadron (Away until 2025-01-11).22:43:19
11 Jan 2025
@orzklv:matrix.org@orzklv:matrix.org left the room.04:07:35
@dgrig:erethon.comdgrig joined the room.07:49:50
@sigmasquadron:matrix.orgFernando Rodrigues changed their display name from SigmaSquadron (Away until 2025-01-11) to SigmaSquadron.15:06:40
@pandapip1:matrix.orgpandapip1 joined the room.21:22:18
12 Jan 2025
@strutztm:strutztm.de@strutztm:strutztm.de joined the room.00:23:59
15 Jan 2025
@ss:someonex.netSomeoneSerge (back on matrix) changed their display name from SomeoneSerge (utc+3) to SomeoneSerge.19:01:46
18 Jan 2025
@sunny.nc:matrix.orgsunny.nc joined the room.12:48:54
19 Jan 2025
@rgrunbla:matrix.orgReventlov left the room.09:36:52
25 Jan 2025
@mlieberman85:matrix.orgMichael Lieberman left the room.04:30:18
27 Jan 2025
@julienmalka:matrix.orgJulienHello, shameless plug: I have written a research paper (and a blog post) about the bitwise reproducibility levels in nixpkgs -> https://luj.fr/blog/is-nixos-truly-reproducible.html14:49:38
@julienmalka:matrix.orgJulienThe paper is here: https://hal.science/hal-0491300714:50:29
@mschwaig:matrix.orgMartin SchwaighoferCongrats! I read the post and upvoted it on HN, will read the paper in the following days. 😊15:35:49
@mschwaig:matrix.orgMartin Schwaighofer* Congrats! I read the post and upvoted it on HN. It's a great post. Will read the paper in the following days. 😊15:36:24
@me:linj.techlinjHow do you treat FODs, such as source codes of packages, in your experiment? Are they substituted from cache.nixos.org or built locally? Are they treated like other packages when classified into reproducible, rebuildable and non-rebuildable? I skimmed through your blog post and paper but did not find this information.16:18:36
@julienmalka:matrix.orgJulienwe did not rebuild the FODs16:19:24
@julienmalka:matrix.orgJulienThey were substituted from the cache16:19:40
@julienmalka:matrix.orgJulienAnd did not count in the statistics16:19:49
@atemu12:matrix.orgatemu12FODs aren't really interesting from a r13y standpoint; they are bit-reproducible by definition.16:20:28
@atemu12:matrix.orgatemu12Their primary issue is source availability16:20:42
@atemu12:matrix.orgatemu12 As long as you can get a FOD from somewhere, it doesn't matter 16:21:12
@julienmalka:matrix.orgJulienI'm also interested in the question: how much of nixpkgs can we rebuild without the cache (in which cas we would need to rebuild the FODs to check if source is still available), but we did not answer this question in this paper16:21:13
@raboof:matrix.orgraboof Atemu: that is only true if you trust the original committer and hydra not to collude on you - which is somewhat safe to assume but also good to check, in theory. 16:22:23
@atemu12:matrix.orgatemu12That's a valid issue but again separate from r13y IMV16:23:13

Show newer messages


Back to Room ListRoom Version: 6