-
Notifications
You must be signed in to change notification settings - Fork 525
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
Can't download package with '+' in version string from TeamCity #2261
Comments
Sorry with latest release 4.5.1, the issue seems still exists. From the stack trace, the error was thrown in NuGetV2.download method, not the places where you have changed in commit a46c0fd. And also I would think it maybe better to be escaped when the url is just fetched, instead of when it is used. Paket/src/Paket.Core/NuGetV2.fs Line 929 in da5ff5a
|
I reverted it and tried 94560b5. can you please retry with 4.5.2 or send another potential fix? |
4.5.2 didn't fix the issue as Paket/src/Paket.Core/NuGetV2.fs Line 945 in e43745a
+ not encoded. I have created a pull request for the proper fix.
|
Description
We used SemVer 2.0 versioning for some of our package. e.g. the package name could be:
MyPackage.1.2.0-master+aaabbb.nupkg
.The metadata section was recently added to the package. When it was not there, paket worked fine. However, when we tried to add the metadata section with
'+'
,paket update
failed with 404 return from TeamCity. See the stacktrace below.What I found is that the url does return 404 when manually accessed, however, it was just because the
'+'
was not escaped to%2B
. If I change the url tohttp://TeamCity/guestAuth/app/nuget/v1/FeedService.svc/download/WebServices_NuGetPackage/36664:id/MyPackage.1.2.0-master%2Baaabbb.nupkg
TeamCity returns the package fine. Sounds like we should escape the url?Repro steps
Please provide the steps required to reproduce the problem
Create a package with name MyPackage.1.2.0-master+aaabbb.nupkg on TeamCity.
Install the package using paket.
Expected behavior
Should install the package correctly.
Actual behavior
404 error and fail to install.
Known workarounds
No.
The text was updated successfully, but these errors were encountered: