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

Issue with paket and third party Nuget server when revision number is zero #1239

Closed
mvkara opened this issue Nov 19, 2015 · 2 comments
Closed

Comments

@mvkara
Copy link

mvkara commented Nov 19, 2015

Some of the proprietary package systems take the version number too literally and don't include the "zero" in the HTTP request to their server. I'm wondering if we can make it more forgiving and allow it to try 3.6 and 3.6.0 as one and the same?

e.g

Paket failed with:
Couldn't get package details for package RhinoMocks 3.6 on http://{third-party-server}

When trying to restore packages it gives me the error:

Paket failed with:
Could not retrieve data from http://{third-party-server}/Packages(Id='RhinoMocks',Version='3.6.0')

Looking at the package for RhinoMocks when you download it from nuget.org the version is coded as "3.6". So in this case the third party server (Proget) assumes this is the one and true version number.

Message from output:
Something went wrong while downloading RhinoMocks 3.6.0
Message: Could not retrieve data from http://{third-party-server}/odata/Packages(Id='RhinoMocks',Version='3.6.0')
Message: Invalid URI: The hostname could not be parsed.

Hardcoding 3.6 in the paket.lock file works in this case works and allows the build to proceed.

@forki forki closed this as completed in 3a6fda8 Nov 19, 2015
@forki
Copy link
Member

forki commented Nov 19, 2015

In the latest version, I changed it back and don't write normalized version into the lock file

@mvkara
Copy link
Author

mvkara commented Nov 19, 2015

Nice turnaround. Thanks
On 19 Nov 2015 7:37 PM, "Steffen Forkmann" [email protected] wrote:

Closed #1239 #1239 via 3a6fda8
3a6fda8
.


Reply to this email directly or view it on GitHub
#1239 (comment).

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

2 participants