Roman Melnikov

Is there a chance that you're using the old version of `deploy-rs` in one of the places?

> But the deploys should have the same versions of deploy-rs on both sides, right? Ugh, this is tricky, see https://github.com/serokell/deploy-rs/pull/207. Before this PR, `activate-rs` script always used the version...

> I'm using the nixpkgs version (master branch) because rust takes forever to compile Hmm, the version from the current nixpkgs master seems to be new enough.

> Got this behaviour if deploying the same closure, and previously i somehow reached a state where the canary file is persistent. I saw such a behaviour previously as well....

The issue with ``` ⭐ ❌ [activate] [ERROR] Error waiting for confirmation event: Timeout elapsed for confirmation ``` returning 0 exit code was fixed by #246

@notgne2, may I ask you to squash and rebase your branch before merging?

Hmm, `x86_64-linux` deployments to `x86_64-darwin` work for me with `--remote-build`. I didn't really try to deploy anything the other way around :thinking:

Does your profile use IFD by any chance?

> I had to disable the checks - but I am still getting a warning The warning is somewhat expected since `deploy-rs` expects `deploy` flake outputs that aren't "standard" flake...

I agree that > Are there any easy alternatives to adding integration of it, such as wrapping `deploy` with something that replaces the `nix` binaries with `nom` binaries? Would be...