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

lichking does not support alternative registries #70

Closed
jrpascucci opened this issue Jan 22, 2020 · 2 comments · Fixed by #72
Closed

lichking does not support alternative registries #70

jrpascucci opened this issue Jan 22, 2020 · 2 comments · Fixed by #72

Comments

@jrpascucci
Copy link

Cargo lichking with configured alternative registries does not function.

cargo lichking list
warning: IANAL: This is not legal advice and is not guaranteed to be correct.
error: failed to parse manifest at C:\projects\cic\master\srv\jaims\validator\Cargo.toml

Caused by:
the cargo feature alternative-registries requires a nightly version of Cargo, but this is the dev channel

There is no alternative-registries feature any more, it's been stabilized at .34

(FYI: I'm poking around on how to bring it up to .41, which has lots of errors, but I have a problem in that I have to go through a corporate process before I would be allowed to do a pull request)

@jrpascucci jrpascucci changed the title Update crates crate to .34 to support alternative registries lichking does not support alternative registries Jan 22, 2020
@Nemo157
Copy link
Owner

Nemo157 commented Jan 23, 2020

If .41 has enough breaking changes in the cargo API it may be time to switch to cargo-metadata, if it provides all the details needed.

That said, I'm tempted to start recommending using cargo-deny and cargo-about instead and deprecate cargo-lichking.

@Nemo157
Copy link
Owner

Nemo157 commented Feb 8, 2020

I don't have anything I can test this with easily, but 0.9.0 is now using cargo-metadata, so as long as the underlying cargo it's calling into supports alternate registries it should work.

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

Successfully merging a pull request may close this issue.

2 participants