-
Notifications
You must be signed in to change notification settings - Fork 585
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
Default to NuGet.org in PublishUrl #1241
Comments
I conform the bug:
|
That's an issue in nuget, right? But can you send a pr that helps us?
|
seems to be as being a blocking issue for next upcoming milestone release 3.5I also just execute without -source parameter&"D:\GitHub-OpenSource\xyz\_CreateNewNuGetPackage\DoNotModify\NuGet.exe" push "D:\GitHub-OpenSource\xyz\New-NuGetPackages\xyz-beta.nupkg" and the error shows up: Source parameter was not specified. with -source parameter&"D:\GitHub-OpenSource\xyz\_CreateNewNuGetPackage\DoNotModify\NuGet.exe" push "D:\GitHub-OpenSource\xyz\New-NuGetPackages\xyz-beta.nupkg" -source nuget.org and the error shows up: WARNUNG: No API Key was provided and no API Key could be found for 'https://www.nuget.org/api/v2/package'. To save an API Key for a source use the 'setApiKey' command.
Pushing xyz-beta.nupkg to 'https://www.nuget.org/api/v2/package'...
PUT https://www.nuget.org/api/v2/package/
Unauthorized https://www.nuget.org/api/v2/package/ 1201ms
Bitte stellen Sie Anmeldeinformationen zur Verfügung für: https://api.nuget.org/v3/index.json
UserName: The NuGetConfig at %AppData%\NuGet\NuGet.config is as follows:<?xml version="1.0" encoding="utf-8"?>
<configuration>
<disabledPackageSources>
<add key="Microsoft and .NET" value="true" />
</disabledPackageSources>
<packageSources>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
<add key="nuget.org" value="https://www.nuget.org/api/v2/" />
NuGetPackages" />
</packageSources>
<apikeys>
<add key="https://www.nuget.org" value="xxxxxxxxxxxxxxxxxxxxxx" />
<add key="http://nuget.gw.symbolsource.org/Public/NuGet" value="yyyyyyyyyyyyyyyyyyyyyyyyyyyyy" />
</apikeys>
<packageRestore>
<add key="enabled" value="True" />
<add key="automatic" value="True" />
</packageRestore>
<bindingRedirects>
<add key="skip" value="False" />
</bindingRedirects>
<activePackageSource>
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</activePackageSource>
</configuration> Tested with NuGet Version: 3.5.0.1520 |
Nearly a year later and ran into this again. Had to roll back my NuGet client to 3.3.0.212 (a version I just happened to have lying around for another project). |
Well, I just started on a PR for this and found, to my surprise, that FAKE does support this. However, the parameter name is Perhaps it should default to |
Yes the default should be changed. A PR would be welcome. |
We got this now in https://www.nuget.org/packages/FAKE/4.61.2 thanks to @zvirja |
Description
New versions of NuGet require source be specified, but FAKE's NuGetHelper does not provide a means of doing so.
Repro steps
Using the latest NuGet client, attempt to publish a package.
Expected behavior
The package is published.
Actual behavior
NuGet spits out this error:
Known workarounds
NuGet 3.4.4 apparently fixes another regression so that the config could be overridden. Without that, I don't know of any workarounds.
Related information
The text was updated successfully, but these errors were encountered: