Ricky Hosfelt

Thanks for the cc @kbknapp I'm in the middle of wrapping up at my current job, but I should be more free starting next week to really look into this...

@svenstaro Yes I have! Progress is moving slowly, but I am working on it :) starting the new job at the same time is tough though

@svenstaro Thank you very much for keeping me honest! So, I am working on this; however, I have been doing so offline because I see a lot of little things...

Hi @warner I am not able to recreate this on MacOS. I copied both the same project's `Cargo.toml` and, for fun/trying to really confuse `cargo-outdated`, a different and more complicated...

I agree that’s probably what’s happening, I’ll boot up my Ubuntu VM and try there soon, thanks for all the wonderful info it will definitely help.

After diving into this I found it is an intended affect of the Cargo API. Looks like https://github.com/rust-lang/cargo/issues/1423 is an (older) issue tracking the affect of this on some projects....

The bug linked in that issue (https://github.com/rust-lang/cargo/issues/4992) is exactly what we’re seeing here as well, it was just closed in favor of the original issue. I did do: ``` mkdir...

Sorry it has taken so long to get back, can you provide me a `Cargo.toml` that reproduces the issue? Thanks!

If I understand correctly you have an internal crate with the same name as another dependency? Basically this happens when a crate with the same name is used in the...

Thanks so much! This very helpful I'll see if we can work on a fix for this, it appears to be pulling in the direct path and a path from...