-
Notifications
You must be signed in to change notification settings - Fork 520
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 when --keep-patch argument is used #2048
Comments
I used Foobar.Service (and https://www.myget.org/F/foobar) just as a placeholder because I didn't want to use the real package name as it would reveal information about our company's proprietary components. The package that causes this issue for us does exist and if the command is run without the |
Ok but that makes it basically impossible for me to reproduce. Any other ideas how I could reproduce it? |
Reproducing issue fsprojects/Paket#2048 * Changed source * Removed Microsoft.CodeAnalysis.Common * Added e5r.krunt (only available in myget-feed) and Newtonsoft.Json
Here is a simple repro: https://github.com/Gonnagle/paket-multiple-sources-test/releases/tag/paket-isssue-2048-repro Executing Edit: And |
I would guess that Shouldn't --keep-patch take the With another source and a nuget with only a released version prerelease flag removed from the dependencies file the command seems to succeed: https://github.com/Gonnagle/paket-multiple-sources-test/releases/tag/paket-issue-2048-no-prerelease). |
please give it another try with latest |
The latest patch seems fix the issue. Thanks you for the quick response :) |
When using the latest Paket (3.30.2), if
paket install --keep-patch --redirects --createnewbindingfiles --clean-redirects --force --verbose
command is executed withpaket.dependencies
andpaket.lock
files that look like the simplified examples below, the command will fail with the following error:For some reason Paket tries to download Foobar.Service from nuget.org even though according to paket.lock file it should be downloaded from myget.org. I was not able to test what happens if I remove nuget.org source as our private MyGet feed contains only our proprietary packages. I did however change the order of the sources in dependencies file with no effect. The latest version of Foobar.Service on MyGet at the time was 1.2.0-alpha1.
I was able to see from the log file that this was not the only instance where Paket tried to download our proprietary package from nuget.org, but in those intances it correctly used myget.org feed after nuget.org failed. To me it seems that there should be no reason why Paket would need to first check nuget.org if lock file says that the package came from another feed.
This might not be directly related to this issue but Paket doesn't seem to use
https://api.nuget.org/v3/index.json
source as defined but instead it useshttp://www.nuget.org/api/v2
according to the log file.paket.dependencies
paket.lock
The text was updated successfully, but these errors were encountered: