-
Notifications
You must be signed in to change notification settings - Fork 26
rust packages get desynched #7
Comments
Looks like this is still happening for OS X.
|
That's a very strange error. I don't know that it's related to this issue though, which is about the version of rustc being inconsistent. Your error seems to be a bug in Cargo? cc @alexcrichton |
That... is quite odd! I don't know how Cargo got connected with |
@alexcrichton I don't think so. Is there anything I can give you to help with debugging?
|
@Hoverbear OSX uses |
@sfackler That's empty too.
It's a bit odd... I ran Rustup again and got the same error, but it appears Cargo is now reporting it's up to date.
|
The reason the combined packages are desynced is because buildbot is using an empty commit ID for synchronization: http://buildbot.rust-lang.org/builders/nightly-dist-packaging-win-64/builds/48/steps/checking%20for%20synced%20dist%20builds/logs/log |
Fixed. |
@brson You rock! |
Although the rustc packages appear to keep their revisions in sync now, the combined rust packages do not. Probably I picked the wrong unique id to synchronize on that wasn't actually unique.
The text was updated successfully, but these errors were encountered: