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

Unexpected dependency resolution (duplicated crate when unification is possible) #14784

Closed
bestdevever123 opened this issue Nov 5, 2024 · 1 comment
Labels
A-dependency-resolution Area: dependency resolution and the resolver C-bug Category: bug S-triage Status: This issue is waiting on initial triage.

Comments

@bestdevever123
Copy link

bestdevever123 commented Nov 5, 2024

Problem

I have a project with maturin 1.7.4, that depends on python-pkginfo, that depends on zip = { version = ">=0.6,<2", default-features = false, features = ["deflate"] }, and maturin itself depends on zip = { version = "0.6.1", default-features = false, features = [ "bzip2", "deflate", "time", ] }.
I would expect the dependency resolver to unify the zip version to 0.6.6, but instead, I get both zip 0.6.6 and zip 1.1.4

Steps

cargo new --lib testing
cd testing/
cargo add maturin
cargo tree | grep zip

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.82.0 (8f40fc59f 2024-08-21)
release: 1.82.0
commit-hash: 8f40fc59fb0c8df91c97405785197f3c630304ea
commit-date: 2024-08-21
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 24.4.0 (noble) [64-bit]
@bestdevever123 bestdevever123 added C-bug Category: bug S-triage Status: This issue is waiting on initial triage. labels Nov 5, 2024
@epage epage added the A-dependency-resolution Area: dependency resolution and the resolver label Nov 5, 2024
@ehuss
Copy link
Contributor

ehuss commented Nov 5, 2024

Thanks for the report! I believe this is the same as #9029, so closing in favor of that.

@ehuss ehuss closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-dependency-resolution Area: dependency resolution and the resolver C-bug Category: bug S-triage Status: This issue is waiting on initial triage.
Projects
None yet
Development

No branches or pull requests

3 participants