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
bug: cannot apply without --impure
#202
Comments
I also saw a similar issue. This happens if I made some changes to my config without committing everything. The exact error message is I patched colmena to disable its use of pure mode: https://github.com/xddxdd/nixos-config/blob/11358a9fddadb544e85a2ecba1aaa987023e98ed/patches/colmena-disable-pure-eval.patch But I'm not sure if this is the correct approach. |
Ah yeah, I usually have a least a few uncommitted changes laying around so I didn't even think about that, but you are right, if I stash everything the error goes away. This seems to be a different definition of "pure" than Nix itself, which is perfectly happy to build an unclean tree in "pure" eval mode itself, and until recently it seems, so was Colmena |
Running into the same issue since the last update of my flake. |
I would have imagined that this line would take care of locking the flake: So something more complex must be going on 🤔 |
Also impacting us, was a pita to track down this issue as well |
As of a recent update of nixos-unstable (maybe 2-3 weeks ago), I haven't been able to run
colmena apply
without adding the--impure
argument due to colmena wanting to make some lockfile changes to it's "Internal Colmena Expressions" flake that get's placed in the/tmp
directory.I am a bit surprised nobody else reported this, so perhaps there is something about my particular flake (which is quite complex at this point) that could be causing this, but in any case, since it seems to be an internal colmena function to create this temporary flake, I figured it was worth reporting.
It may be as simply as running a
nix flake lock
on this temporary flake before doing anything else, but I don't understand enough what colmena is doing (yet) to say for sure.The text was updated successfully, but these errors were encountered: