-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current implementation cannot handle multiple crates with the same lib
name
#22
Comments
Yes, in this instance the crate is used both as build dependency and normal dependency. I've ran into this multiple times myself. Thanks for filing the bug. |
Thanks for the tool! It promises to be really helpful |
I'm attempting to use this on https://github.com/libra/libra and it's failing with a similar error:
But admission_control_proto is not listed twice anywhere that I can see. Looks like the error message might be incorrect? |
PRs to fix it are welcome! |
@metajack The problem can be fixed by this. (I don't know why) for (to_pkg, deps) in resolve.deps(from) {
+ // `Resolve::deps` rarely returns multiple same `Dependenc`ies.
+ let deps = deps.iter().collect::<BTreeSet<_>>(); But unfortunately
[dependencies]
futures = "0.1.28"
futures03 = { version = "=0.3.0-alpha.17", package = "futures-preview" } |
Still not working even though replacing
|
When running
cargo +nightly udeps
against https://github.com/habitat-sh/habitat:I know
is listed as a known bug in https://github.com/est31/cargo-udeps/blob/master/README.md#known-bugs, but I couldn't find an issue that's tracking it. Since the project I work on won't be able to make use of
udeps
until this is resolved, having an issue I can subscribe to will help ensure that I can use it when that bug is fixed.The text was updated successfully, but these errors were encountered: