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

cargo install --locked has warnings about yanked packages #256

Open
jtmoon79 opened this issue Mar 22, 2024 · 0 comments
Open

cargo install --locked has warnings about yanked packages #256

jtmoon79 opened this issue Mar 22, 2024 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers P1 important

Comments

@jtmoon79
Copy link
Owner

Problem

Installing s4 0.6.69 with --locked.

As of today, cargo has two warnings.

$ cargo install --locked super_speedy_syslog_searcher
    Updating crates.io index
  Downloaded super_speedy_syslog_searcher v0.6.69
  Downloaded 1 crate (461.5 KB) in 0.00s
  Installing super_speedy_syslog_searcher v0.6.69
warning: package `crc-catalog v2.3.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `wasm-bindgen v0.2.88` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
  ...
  • warning: package `crc-catalog v2.3.0` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
  • warning: package `wasm-bindgen v0.2.88` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

Solution

For the warning regarding crc-catalog v2.3.0 I created Issue mrhooray/crc-rs#116 .

Oddly, for warning regarding wasm-bindgen v0.2.88, cargo tree does not show any such crate as a dependency. 🤔

@jtmoon79 jtmoon79 added bug Something isn't working good first issue Good for newcomers P1 important labels Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers P1 important
Projects
None yet
Development

No branches or pull requests

1 participant