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

Uses git-based package registry instead of sparse registry by default #477

Open
w-flo opened this issue Jun 22, 2023 · 0 comments
Open

Uses git-based package registry instead of sparse registry by default #477

w-flo opened this issue Jun 22, 2023 · 0 comments

Comments

@w-flo
Copy link

w-flo commented Jun 22, 2023

Thank you for cargo-geiger!

Cargo has now switched to using the sparse registry by default, so I have removed the git-based registry files from my system. However, when I try to use current cargo-geiger 0.11.6, it will download the old git-based registry again.

I believe it should be enough to bump the cargo dependency in cargo-geiger to 0.71 to fix this. At least it seemed to work for cargo-outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant