Need helpers for debugging lock file issues

[TomMD]

Could we get a debug or GNU-style -vvv for spewing information? I'm in a situation where cargo2nix complains:

$ nix run github:cargo2nix/cargo2nix
error: the lock file ....path.../Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

But cargo generate-lockfile does not improve the situation. If I could pass flags to cargo through nix and cargo2nix such as --offline then I'd try that.

[psionic-k]

Probably low-hanging bug. I was going to do a round of updates.

What's your nix version by the way?

I wouldn't worry about a flag. This is almost surely going to be a one-time fix in one place rather than generally useful behavior

[TomMD]

It's a nixpkgs on Debian-based Linux:

$ nix --version
nix (Nix) 2.13.2

[TomMD]

Looking forward to the updates,thanks for maintaining!

[psionic-k]

Try passing "--locked" to a regular cargo build to verify that the Cargo.lock in source is up to date. It needs to be in version control. https://doc.rust-lang.org/cargo/commands/cargo-rustc.html#manifest-options