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

Unable to check for yanked crates when crates.io git registry is outdated #508

Closed
jplatte opened this issue Apr 7, 2023 · 0 comments · Fixed by #513
Closed

Unable to check for yanked crates when crates.io git registry is outdated #508

jplatte opened this issue Apr 7, 2023 · 0 comments · Fixed by #513
Labels
bug Something isn't working

Comments

@jplatte
Copy link
Contributor

jplatte commented Apr 7, 2023

Describe the bug

When the git-based crates.io registry is outdated or missing, cargo deny fails to check for yanked crates, with a mediocre error message:

warning[index-failure]: unable to check for yanked crates
  ┌─ /home/jplatte/code/ruma/.deny.toml:1:1
  │
1 │ # https://embarkstudios.github.io/cargo-deny/checks/cfg.html
  │ ^ lint level defined here
  │
  = failed to find crate in git index

To Reproduce

  • Delete ~/.cargo/registry

  • (May not be needed) Add the following to ~/.cargo/config.toml

    [registries.crates-io]
    protocol = "sparse"
  • Run cargo deny check in some project

Expected behavior

Yanked crates should still be checked ideally :)

@jplatte jplatte added the bug Something isn't working label Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant