Crate failed to unpack on Windows (os error 3) - path name too long

[UK992]

unable to get packages from source

Caused by:
  Failed to unpack package `servo-skia v0.20130412.3`

Caused by:
  The system cannot find the path specified. (os error 3)

Failed if path has spaces servo/servo#9442
and also for unknown reason servo/servo#10089 (maybe too many subfolders or capital letters?)
or something wrong with crate servo-skia?

[alexcrichton]

What version of Cargo were you using for this? It looks like this may be similar to #2309 where the path name is just too long in the servo-skia crate

[UK992]

2016-03-04 version for servo/servo#10089 and 2015-10-01 for servo/servo#9442 (based on github history)

[alexcrichton]

The "spaces in path" mentioned in servo/servo#9442 I don't think have anything to do with Cargo. It sounded like that was primarily for makefiles and various scripts here and there which didn't properly escape spaces, but Cargo doesn't have to worry about any of that.

For servo/servo#10089 the error message is "The system can not find the path specified" for a path name with 263 bytes in it, which on my system returns "The filename or extension is too long". I suspect a different version of Windows may have been in use which had a different error for the report.

[CryZe]

I just encountered this with neon-sys. Apparently cargo can't unpack crates that cause paths that are too long. This is not an issue of Windows though, as I was able to manually unzip it with WinRAR. So this is definitely a bug in cargo.

This was the path that was causing trouble:

C:\Users\Christopher\.cargo\registry\src\github.com-88ac128001ac3a9a\neon-sys-0.1.9\node_modules\node-gyp\node_modules\request\node_modules\har-validator\node_modules\is-my-json-valid\node_modules\generate-object-property\node_modules\is-property\is-property.js

[vae520283995]

I have the same problem