I am using a mirror of crates.io on my local network. It is updated manually by ticket with long delays, so I am trying to find a solution that doesn't require an update. I have a project that requires the dlmalloc crate. My mirror has dlmalloc up to version 0.2.9. My project fails to build because it is looking for, and failing to find, version 0.2.10. I have looked exhaustively through every Cargo.toml in the project, and everywhere dlmalloc is needed, if it doesn't have a version number, I manually specify 0.2.9 in it. Furthermore, I haven't found any Cargo.tomls that specify needing version 0.2.10.

To my mind it should not be looking for 0.2.10 at all, but despite these steps, when I run cargo build, I still get the error that it fails to find dlmalloc version 0.2.10. So I think my main question is, why is it still looking for version 0.2.10, when it explicitly shouldn't be?

I have a separate problem when trying to run a MWE to solve this, which may be helpful. I created a test_project, left it completely empty, and added one common dependency (rand 0.8), and as a diagnostic, ran cargo tree -i test_project. The output is just "test_project v0.1.0 (/path/to/test_project)" I don't know what to expect from cargo tree, but I was under the impression it should show the rand dependency in the tree somewhere. I cannot run cargo tree on the main project, as it does not build.

1 post - 1 participant

Read full topic