Jacob Finkelman

Transferred to Cargo. IMO one of the big problems blocking this is the error messages. The current Resolver has pretty bad messages, it just reports on the last thing that...

looks like I have hit: https://support.google.com/chrome/answer/1342714 So it may be related to my using "https everywhere"

Those links should probably be `'://twiecki.github.io/...'` insted. I don't know how to get your static site generator to do the, sorry.

If you are a maintained project and your dependency has not been updated, then a fork of the dependency seams like the honest way to do things.

Ya this is going to be tricky to solve. It is related to https://github.com/rust-lang/cargo/issues/2589 but in this case it is a conflict between two different packages build dependencies. If we...

I can confirm that this is not the new error we just added. So I don't think it is a regression. An ideal cargo would allow this, but I don't...

I made an issue to link all the discussions about this to. So here gose https://github.com/rust-lang/crates.io/issues/7310

If there were progress it would be listed here. It is still a hard problem.

As you point out, once you have a complete dependency graph selected it is fairly easy to check before linking whether this particular call will lead to linking multiple crates...

Looking at the code, it looks like it sets the [`retry_after` field](https://github.com/rust-lang/crates.io/blob/932c6a721b2f63c91148f41a27883d15588b2d8f/src/publish_rate_limit.rs#L40) and then uses it in the [response](https://github.com/rust-lang/crates.io/blob/d20f081fcb53a47d7a5b79bcb0629f1953b55f36/src/util/errors/json.rs#L139-L151) with a fairly reasonable explanation in the body. I wonder if...