In reply to @p14:matrix.org

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?

Why do I see this difference between the builders of the same unresolved and resolved content-addressed derivation? 🤔

diff /nix/store/q2nzjyqf4w19w3mgbkn34k2as5hrvwh1-builder.sh /nix/store/ckzrg0f0bdyx8rf703nc61r3hz5yys9q-builder.sh
22c22
<     printf '%s ' "${propagatedUserEnvPkgs[@]}" > $out/nix-support/propagated-user-env-packages
---
>     printf '%s ' $propagatedUserEnvPkgs > $out/nix-support/propagated-user-env-packages

In reply to @roberthensing:matrix.org
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

I asked this on twitter but maybe here is a better place.
On my MacOS Nix installation (2.26) I'm surprised in my flake project how often I hit:

unpacking 'github:NixOS/nixpkgs/b7ba7f9f45c5cd0d8625e9e217c28f8eb6a19a76' into the Git cache.