Latest cargo can't parse Cargo.toml?

[MagaTailor]

I'm getting a strange error from url 0.5.9:

error: unable to get packages from source

Caused by:
  failed to parse manifest at `.cargo/registry/src/gitproxy.zycloud.tk-48ad6e4054423464/url-0.5.9/Cargo.toml`

Caused by:
  could not parse input as TOML
.cargo/registry/src/gitproxy.zycloud.tk-48ad6e4054423464/url-0.5.9/Cargo.toml:14:3 expected a newline after table definition

You probably know what's happening - cargo bug, breaking change?

[metajack]

@alexcrichton Ideas?

[alexcrichton]

Yes this was a bug fix to TOML parsing in toml-rs/toml-rs#94, but Cargo has not yet been upgraded to have that bugfix. That is being done as part of rust-lang/cargo#2680 in a way that will not emit this error.

I don't really know why you would be seeing this error unless you custom compiled Cargo against a newer version of TOML manually, none of our releases should have this.

[metajack]

We're using 2016-05-12 nightly.

[MagaTailor]

I don't recall modifying any dependencies and the latest git source doesn't produce a cargo like that. I was using different cargo versions though; maybe 0.11 doesn't go well with 0.10 source or some other combination.
Oh well.

[SimonSapin]

If this keeps being a problem I can publish url 0.5.10 with more newlines in Cargo.toml.

[SimonSapin]

(1.x versions do that already.)

[xpe]

@SimonSapin yes, it would be useful to push a new version in the 0.5.x series with e362e13

warning: TOML file found which contains invalid syntax and will soon not parse
at `/Users/xpe/.cargo/registry/src/gitproxy.zycloud.tk-1ecc6299db9ec823/url-0.5.9/Cargo.toml`.

The TOML spec requires newlines after table definitions (e.g. `[a] b = 1` is
invalid), but this file has a table header which does not have a newline after
it. A newline needs to be added and this warning will soon become a hard error
in the future.