Nightly Cargo tracking broken

[alexcrichton]

We changed how Cargo's released, now we're not publishing manifests. Although this works for rust-packaging, it doesn't work for rustup. We need to figure out a solution. (can't believe I forgot about this)

[jchlapinski]

@alexcrichton could You please provide more background on why that was changed? Is there an ongoing change on the way Rust+Cargo will be released?

[Diggsey]

Yes, I was trying to find out earlier about the change and was frustrated by the lack of any information...

[tbu-]

Is there a way I can fix my local Cargo until this is resolved? I still have the one with rust-lang/cargo#3340.

[jchlapinski]

Is there a way I can fix my local Cargo until this is resolved? I still have the one with rust-lang/cargo#3340.

@tbu- Actually You can, as described here: rust-lang/cargo#3340 (comment)
For me on Ubuntu 16.04 I had to do:

> export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt

[carols10cents]

@jchlapinski @Diggsey what information do you need? is there something you would do with that information?

[alexcrichton]

@jchlapinski @Diggsey the "information" here unfortunately is essentially "complete and total knowledge of Rust's release infrastructure". There has been quite a few bugs in the past few weeks either related to Cargo or distribution infrastructure, all of which are getting combined into a so-called perfect-storm of bugs to prevent Cargo from being fixed for quite some time.

I personally hope to fix this as soon as possible. There's a Mozilla work week in Hawaii right now so I don't have a ton of time, but when I get a chance I'll try to watch builds and such. My current attempt to fix this is rust-lang-deprecated/rust-buildbot@92a5919, we'll find out in the morning if it worked.

[alexcrichton]

Note that this bug was mostly just a reminder to me/brson, there's not a lot actionable beyond that unfortunately.

[jchlapinski]

Ok, I can see now, that my previous question might seem somewhat hostile and critical, while I was just genuinely curious. I tought maybe there is on ongoing effort to integrate cargo with rust under a single versioning scheme, maybe even integrate it into the rust repo? It would make sense to me as it would ease the maintenance somewhat. I looked for a discussion on this and could not find any, hence I asked here.

@alexcrichton thanks for Your time explaining.
@carols10cents I was considering helping, as Alex mentioned that a solution was needed. What do You need this information for?

Peace

[carols10cents]

@carols10cents I was considering helping, as Alex mentioned that a solution was needed. What do You need this information for?

I wanted to see if you had a dependency on the internals of rust's release infrastructure, and to see if I could get you the actual information you needed without taking up any of Alex's time.

[Diggsey]

the "information" here unfortunately is essentially "complete and total knowledge of Rust's release infrastructure"

We changed how Cargo's released

Information relevant to the actual "change" would be sufficient, I don't know why you'd assume that I wanted a complete description of the infrastructure from scratch...

A description of what the fallout will look like for a rustup user would also be helpful.

I presume this change was implemented in a PR somewhere?

[carols10cents]

A description of what the fallout will look like for a rustup user would also be helpful.

Once this issue is fixed, rustup users should not notice any change. The change is purely internal implementation.

[brson]

Looks like @alexcrichton is working on the fix rust-lang-deprecated/rust-buildbot@92a5919

[alexcrichton]

Ok, fix looks like it's working:

$ cargo +nightly version
cargo 0.16.0-nightly (built 2016-12-06)

Closing this but I'll try to write something up about this at some point.

@Diggsey Cargo nightlies are now produced from Travis/AppVeyor, not buildbot, which basically just changed how everything is laid out.

[tbu-]

What do I need to do to receive this fix? Update rustup?

[lambda-fairy]

@tbu- Running rustup update works for me. As @carols10cents said above: the issue was completely server-side, and so you don't need to do anything specific to receive the fix.

[jchlapinski]

@lfairy after rustup update I still have:

> rustc --version
rustc 1.15.0-nightly (ebeee0e27 2016-12-04)
> cargo --version
cargo 0.16.0-nightly (3568be9 2016-11-26)

[jimmycuadra]

I still get cargo 0.16.0-nightly (3568be9 2016-11-26) on both macOS and Linux. Maybe we need to wait for tomorrow's nightly to pick up the changes.

[alexcrichton]

I believe I failed to bust caches this morning, should be good now.

[tbu-]

Works now, thanks!