-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Incompatible with upcoming bare Cargo registry #32
Comments
Hmmm, I guess we could basically do the same thing as we do now but through the 4026 landed in nightly 5 days ago, so it'll land in stable like 4 weeks from that, or does |
It should land as 0.20.0, so 1 or 2 months. I think keeping the code in master until it hits stable is a good idea. |
Eh, the difference between non-bare and bare is only the location of the repo itself (and IIRC |
Doesn't work though:
|
Can you check that that directory is actually a git repository? It works for me, but |
|
Interesting, a manually-cloned bare repo works for me. Try replacing |
|
And it's the same with |
Yep |
That's definitely interesting, but I can't see how I can do anything else than read |
https://libgit2.github.com/libgit2/#HEAD/group/revparse You have to use an |
Because it works:tm:, the more you know Ref: #32
If that's the last thing then I'm gonna release it, if y'all have no objections? |
I don't know. It seems, it works on nightly now, so I have no objections. |
I only use stable so yes. |
Released in |
I'm seeing this issue in v1.3.1.
|
The |
The problem seems to be that it's reading the wrong index. |
The previous code used the directory last-modified date to decide which is the newest index checkout. However, this doesn't account for the possibility of files within the directory that have been touched more recently than the directory itself. I don't know how this situation arises but my guess is it has to do with switching cargo versions back and forth using rustup. Ref: nabijaczleweli#32
rust-lang/cargo#4026 introduced local registry without checkout, and this tool doesn't work since it relies on registry directory structure.
The old format isn't compatible with the new format at all, so choose one:
The text was updated successfully, but these errors were encountered: