Mika Logan
Mika Logan
I'm not sure why that could be, deploy-rs doesn't do anything special when it comes to rollbacks either, it just re-activates the older generation, removes your new generation, then runs...
Could this be solved by just having the values you used out of `deploy-rs-remote` all take `pkgs` as a function? I'm not sure that's much cleaner than changing follows though
You can always run deploy again but with `--auto-rollback false`, which will make it ignore any activation errors but still rollback if there is any connectivity error detected (unless you...
That sounds like an upstream NixOS issue if it's attempting to perform the impossible upon activation and failing, and `--auto-rollback false` should work in your case too (it will fail,...
>At this point might as well rewrite it from scratch. in which case having a referenceable specification would be a good thing! I also _kindof_ wanted to do a lot...
Rollback stuff makes it complicates yes, but at least after our current iteration of the codebase we know _how_ it makes it complicated, so if we include it again we...
I've gotten annoyed a lot by this too, but I think basically this is semi-intentional. This issue used to not exist, instead on rollback we would run the same activation...
I'm not really sure what could have happened here, though I think #59 might help
Is this reproducible now?
Absolutely, but one thing to bare in mind is I would one day like to support deploying multiple profiles to the same node, which will require doing away with our...