nix flake: failed to create symbolic link about crunchy-cli

[bytedream]

@stepbrobd any idea why this fails?
If I'm correct this failure exists since dc6bc0d. Beginning with this commit the native-tls crate got replaced by a fork of it. If I remove the line which overwrites the crate with the fork, the error disappears.

[stepbrobd]

If I'm correct this failure exists since dc6bc0d. Beginning with this commit the native-tls crate got replaced by a fork of it. If I remove the line which overwrites the crate with the fork, the error disappears.

Good catch! The line you mentioned resulted in two `native-tls` entries present in `Cargo.lock`, this is not supported by `buildRustPackage`.

 [[package]]
 name = "native-tls"
 version = "0.2.11"
 source = "git+https://github.com/crunchy-labs/rust-not-so-native-tls.git?rev=570100d#570100d3391bd9aab7a390cfef0d1a28e8efe200"
 ...

 [[package]]
 name = "native-tls"
 version = "0.2.11"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 ...

There are couple ways to solve this:

1. Removing native-tls fork from dependencies, or
2. Writing patch to remove duplicate entries in the Cargo.lock file, or
3. Try using a community maintained toolchain, they might support duplicate entries in Cargo.lock (haven't tested this yet, will look into it).

Related:

• NixOS/nixpkgs#22177
• https://discourse.nixos.org/t/rust-with-git-deps-symbolic-link-error-to-cargo-vendor-dep/28841
• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/rust.section.md

[bytedream]

I removed duplicated entry from Cargo.lock / now only rely on the [patch.crates-io] section in Cargo.toml.
@lachydavies25 you should be able to run it via nix now.