-
Notifications
You must be signed in to change notification settings - Fork 18
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
cargo mn
throws some warns on first build
#285
Comments
The "running The "warning: skipping duplicate package |
Manganese uses a "private" feature flag called "_any-deps" to determine whether any bindep dependency feature flag is enabled. Unfortunately, some parts of the code mistakenly use the name "_any_deps" (with a second "_" instead of a "-") to refer to this feature, which is incorrect. This results in Manganese always emitting a warning that no deps were installed, even when this is not actually the case. Surprisingly, Rust doesn't warn you when you reference a feature flag that doesn't actually exist, which means we never caught this issue in development. This branch fixes that by using the correct name for the feature flag everywhere. Fixes #285
Manganese uses a "private" feature flag called "_any-deps" to determine whether any bindep dependency feature flag is enabled. Unfortunately, some parts of the code mistakenly use the name "_any_deps" (with a second "_" instead of a "-") to refer to this feature, which is incorrect. This results in Manganese always emitting a warning that no deps were installed, even when this is not actually the case. Surprisingly, Rust doesn't warn you when you reference a feature flag that doesn't actually exist, which means we never caught this issue in development. This branch fixes that by using the correct name for the feature flag everywhere. Fixes #285
Reopening to track the second error, and tagging @spookyvision |
the |
Tried running
cargo mn
(with no args) today, and it printed some warnings we might want to address.Then when running melpomene:
The text was updated successfully, but these errors were encountered: