Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

paket install fails on extraction if path is longer than 260 characters #1331

Closed
jschroed opened this issue Dec 27, 2015 · 2 comments
Closed

Comments

@jschroed
Copy link

I'm having an issue with paket when I execute paket in a really long directory name. When I try to run paket update or paket install in my directory with the long name (near or over 260 characters), I get this error message:

Paket failed with:
        Error during extraction of C:\j\workspace\really-long-path-name\another-really-long-directory-name\third-really-name-path-name\last-really-really-long-name\packages\nuget-bot.Microsoft.VisualStudio.Services.Common\nuget-bot.Microsoft.VisualStudio.Services.Common.12.0.21005.1.nupkg.
Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. In rare cases a firewall might have blocked the download. Please look into the file and see if it contains text with further information.

My paket.dependencies has a source line plus this package in it:

nuget nuget-bot.Microsoft.VisualStudio.Services.Common

Microsoft has this information about prefixing paths with "?" to resolve this: https://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath. I'm not sure if this can be applied to paket.

Is this an issue with paket that can be fixed or do I need to make sure our path names in our projects are always shorter than this limit?

Edit:
There was a ticket with using directories with more than 260 character but I think the issue is different: #949

@forki
Copy link
Member

forki commented Dec 27, 2015

Currently this is not supported. We need to use a different api for this,
but I'm not sure when we have it.
On Dec 27, 2015 07:51, "jschroed" notifications@github.com wrote:

I'm having an issue with paket when I execute paket in a really long
directory name When I try to run paket update or paket install in my
directory with the long name (near or over 260 characters), I get this
error message:

Paket failed with:
Error during extraction of C:\j\workspace\really-long-path-name\another-really-long-directory-name\third-really-name-path-name\last-really-really-long-name\packages\nuget-botMicrosoftVisualStudioServicesCommon\nuget-botMicrosoftVisualStudioServicesCommon120210051nupkg
Message: The specified path, file name, or both are too long The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters In rare cases a firewall might have blocked the download Please look into the file and see if it contains text with further information

My paketdependencies has a source line plus this package in it:

nuget nuget-botMicrosoftVisualStudioServicesCommon

Microsoft has this information about prefixing paths with "?" to resolve
this:
https://msdnmicrosoftcom/en-us/library/aa365247%28VS85%29aspx#maxpath I'm
not sure if this can be applied to paket

Is this an issue with paket that can be fixed or do I need to make sure
our path names in our projects are always shorter than this limit?


Reply to this email directly or view it on GitHub
#1331.

@forki forki closed this as completed Dec 28, 2015
@johannesegger
Copy link
Contributor

Isn't it basically this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants