New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nix-copy-closure not working #1530
Comments
Note: I've also experienced this error when using channels. I constructed a channel out of these sources and got this error when the client was attempting to update the channel. |
nix-copy-closure doesn't do anything with nix-env. You can add it to nix-env afterwards by doing a nix-env -i on the derivation. |
Indeed, the usage of copy-closure isn't related to the error you're getting. I've minimized the testcase to:
which still gives the same on
So it's somehow related to import-from-derivation inside |
@dezgeg the dynamic nixpkgs import is probably the problem. Using fetchTarball will probably fix this. See NixOS/nixpkgs#27994 for more discussion about nixpkgs pinning. |
@puffnfresh : fetchTarball does indeed resolve the issue in the repro case. for reference: the tarball url is: https://github.com/NixOS/nixpkgs-channels/archive/96457d26dded05bcba8e9fbb9bf0255596654aab.tar.gz |
To be clear, to get it working I changed repro to this. This sidesteps the need for a bootstrapping nixpkgs and just uses the builtin. Is this what you meant? Obviously in real code we'll need the new fetchTarball that can take a sha. :)
|
nix-env runs nix in read-only mode => IFD does not work there |
Forgive my ignorance, but what is IFD, @globin ? |
@benkolera "import from derivation" - meaning you use Nix to build an output then you import from that output. The Instead, |
I marked this as stale due to inactivity. → More info |
I have a nix package that wraps Amazon Dynamodb Local. I wish to build it on a nixos machine, then nix-copy-closure it to another machine (in this case, a Fedora workstation).
As part of this, I wish to "pin" nixpkgs to a specific version for build repeatability. To achieve this, I'm following the approach detailed here: https://gist.github.com/zimbatm/de5350245874361762b6a4dfe5366530
It seems that nix-copy-closure can't deal with this pinning correctly.
My steps are:
Source machine:
Dest machine:
Expected:
Actual:
Logs:
Source machine:
Target machine:
Code is here:
https://github.com/ephox-services/nix-copy-closure-bug-replication
Thanks!
The text was updated successfully, but these errors were encountered: