-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[workspace] Prereleases with path dependencies fail #7007
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
Comments
I think this is to be expected, caret requirements do not select pre-release versions. The error message could definitely be better. |
ehuss
added
the
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
label
Jun 4, 2019
Is there any selector that would work? Neither |
|
debris
added a commit
to debris/cargo
that referenced
this issue
Jul 30, 2019
bors
added a commit
that referenced
this issue
Aug 1, 2019
improve error message for unmatched prerelease dependencies fixes #7007 error message before: ``` error: no matching package named `a` found location searched: [..] perhaps you meant: a required by package `b v0.1.0 ([..])` ``` error message now ``` error: no matching package named `a` found location searched: [..] prerelease package needs to be specified explicitly a = { version = "0.1.1-alpha.0" } required by package `b v0.1.0 ([..])` ```
alessandrod
added a commit
to aya-rs/aya-log
that referenced
this issue
Apr 23, 2022
Fixes [2022-04-23T08:19:29Z WARN ] Fatal: Invalid TOML file format: Error during execution of `cargo metadata`: error: no matching package found searched package name: `aya-log-common` prerelease package needs to be specified explicitly aya-log-common = { version = "0.1.3-alpha.0" } location searched: /home/alessandro/aya-log/aya-log-common required by package `aya-log v0.1.2 (/home/alessandro/aya-log/aya-log)` See rust-lang/cargo#7007
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
I am not certain this is a bug, but at least it is very surprising to me:
a
andb
b
depends ona
, usinga = {version = "^0.1", path = "../a"}
cargo test --all
worksa
to a prerelease of0.1.1-alpha.0
triggers the following errorSteps
cargo test --all
Possible Solution(s)
It would be great if it either worked, or at least the error message was more clear as to what the actual problem is.
Notes
Output of
cargo version
:The text was updated successfully, but these errors were encountered: