-
Notifications
You must be signed in to change notification settings - Fork 36
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
multirust update
do not fetch newest nightly
#121
Comments
I haven't been able to reproduce this. Locally I have I wonder if something in the metadata got corrupted. There should be a new nightly published tomorrow. Maybe your multirust will successfully update then. |
I saw this problem too, but it has disappeared now. I believe I had a problem with my installation of |
I'm experiencing this now. I ran a
Curiously, there isn't even an entry for 2016-03-19 at http://static.rust-lang.org/dist/ . I did notice that Edit: Turns out cargo runs in spite of the difference in builds. I grabbed the latest x86_64-unknown-linux-gnu.tar.gz as per the instructions on cross-compiling libcore. Edit 2: Odd. The multirust libcore does match the one I grabbed ( Here's the output of
And verbose rustup output:
|
@caipre The date reported by |
@brson Yes, |
The indexing is done as a nightly batch process independently from the rest of the build. It would not surprise me if somehow its indexes got distributed to the CDN before the files its indexing. Ugh... |
Multirust version:
multirust update
output:But what I have seen on https://static.rust-lang.org/dist/ there already are versions for 2016-01-05 and 2016-01-08.
The text was updated successfully, but these errors were encountered: