Skip to content
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

fix: handle renamed dependencies correctly #60

Merged
merged 2 commits into from
Aug 15, 2024
Merged

Conversation

StackOverflowExcept1on
Copy link
Contributor

Resolves #59. See issue for more details. This PR fixes the handling of renamed dependencies (previously bar = { version = "1.0", package = "foo" } was handled incorrectly). I also added .gitignore file.

@d-e-s-o It would be nice to create release on crates.io right after this commit.

@d-e-s-o
Copy link
Owner

d-e-s-o commented Aug 14, 2024

Interesting. Could you add a test case for this issue?

@StackOverflowExcept1on
Copy link
Contributor Author

@d-e-s-o Hmm, I'm not sure how to add complex test, but this fixed my issue in this repo: https://github.com/StackOverflowExcept1on/cargo-bug

@StackOverflowExcept1on
Copy link
Contributor Author

StackOverflowExcept1on commented Aug 15, 2024

I've encountered another issue with renamed dependencies in my workspace. It seems that cargo-http-registry doesn't support the latest changes https://github.com/rust-lang/cargo/blob/master/src/doc/src/reference/registry-index.md. It seems issue #61 occurs because features2 key is not processed. Minimal example: StackOverflowExcept1on/cargo-bug@8c7b35b

@d-e-s-o d-e-s-o merged commit 23578b7 into d-e-s-o:main Aug 15, 2024
6 checks passed
@d-e-s-o
Copy link
Owner

d-e-s-o commented Aug 15, 2024

Thanks!

d-e-s-o added a commit that referenced this pull request Aug 15, 2024
Add a CHANGELOG entry for pull request #60, which fixed handling of
renamed packages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cargo cannot find renamed dependency from crates-io in package from different registry
2 participants