-
Notifications
You must be signed in to change notification settings - Fork 526
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
Improve error message for non-existing nuget feeds #545
Comments
@yreynhout could you please give the corresponding line from the |
@forki An entry that resembles |
I'll take a look tomorrow |
should |
probably all. 2015-01-14 11:15 GMT+01:00 Tomasz Heimowski notifications@github.com:
|
nice yellow warning? |
sometimes nuget v2 feed is also down, so failing because of that seems like an overkill |
Yes a warning is good.
|
cool, will do my best to send a PR today |
Given a computer that has a nuget package source that refers to a local folder on that computer and that local folder DOES NOT EXIST,
When running
paket convert-from-nuget
Then
paket
fails with the correct statement that it can not find part of the local folder (aka path).To be precise, I think it's the implicit (unless
--no-install
was specified)paket install
phase that fails, so the issue might be more general than the conversion from nuget.However, it is non-obvious to an end-user what that path means nor why paket is even looking at that path. So what I'm asking for is a clearer message upon failure or skipping non-existing package sources silently, whichever matches the paket philosophy best.
Additionaly, once the end-user finds out about this, he can remove the culprit nuget package sources from his list of nuget package sources. But alas, that doesn't help, since at that point paket has already copied those sources into its
paket.dependencies
. Perhaps the integrity of the paket sources should be verified as well.The text was updated successfully, but these errors were encountered: