Nix Hackers | 925 Members | |
| For people hacking on the Nix package manager itself | 193 Servers |
| Sender | Message | Time |
|---|---|---|
| 1 Apr 2025 | ||
| 09:30:34 | ||
| I am trying to use nix-store —load-db with a closureInfo registration file. In the closure I put a fixed output deviation for nixpkgs itself: I am baking a machine image with nixpkgs available. One problem though is I can’t easily get my hands on the nixpkgs path. I tried to use fetchClosure, but this doesn’t work on a machine whose nixpkgs path was registered using nix-store —load-db. So it fails when built using the machine image. ‘Nix path-info’ shows that the ca:fixed: metadata is missing, which results in fetchClosure saying that it is input addressed but inputAddressed = false. Should the ca metadata be missing in this scenario? Is there a way to put it there? | 13:09:32 | |
| 13:58:06 | ||
| 13:59:29 | ||
| I don't really follow the reasoning here, https://github.com/NixOS/nixpkgs/issues/393359#issuecomment-2767289529 The build system for Nix 2.24 is already packaged, no? So why would 25.05 sticking to that version of Nix mean having to maintain two build systems? GHC very intentionally did a gradual shift and the Make based build system hasn't been supported as of 9.6.1 from 2023-03-10 latest | 15:37:04 | |
| release is 9.12.2, so that's long past. | 15:37:10 | |
| 2 Apr 2025 | ||
In reply to @p14:matrix.orgRobert Hensing (roberth): I saw your reaction, was what I wrote clear enough, does this sound like an issue or misuse? | 12:46:19 | |
| Why do I see this difference between the builders of the same unresolved and resolved content-addressed derivation? 🤔
| 13:10:54 | |
| I haven't found time to look into this properly, whether this is a bug or a missing feature, or both. The main constraint for closureInfo etc, is that the info needs to be reproducible, so for example no signatures or other mutable store metadata. ca:fixed: seems like something that should be possible to include | 14:08:20 | |
The --load-db format has come up before. It is entirely forward-incompatible, so we may need to introduce any additions as a new format | 14:09:42 | |
In reply to @roberthensing:matrix.orgGlancing at the load db there are signs the signature is there; is it just not being imported properly, I wonder 🤔 | 14:39:37 | |
| emily ElvishJerricco OK we discussed a bunch and we're liking the sort of compromise you all proposed | 20:30:03 | |
| 2.28 in 25.05 has Mic92's combo build (or something like it) | 20:30:27 | |
| 2.28 after 25.05 is componentized | 20:30:36 | |
| 2.29 in all branches has componentized (2.29 is very unimportant on 25.05 except for new version dogfooders) | 20:31:03 | |
| Also when we re-introduce nix git, we should use the componentized version for that | 20:32:23 | |
| how does that sound? | 20:32:27 | |
| I would like to merge Robert Hensing (roberth)'s open PR right away, for sake of the newer versions and git, and also because I like how it makes a package set for the dependencies, even with the monolithic package for Nix itself | 20:33:19 | |