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

Feature request: better message if package ID already exists #9053

Closed
gsscoder opened this issue Jan 13, 2020 · 4 comments
Closed

Feature request: better message if package ID already exists #9053

gsscoder opened this issue Jan 13, 2020 · 4 comments

Comments

@gsscoder
Copy link

@gsscoder gsscoder commented Jan 13, 2020

If package ID exists I get:

info : Push di Tagger.1.0.5.nupkg in 'https://www.nuget.org/api/v2/package'...
info :   PUT https://www.nuget.org/api/v2/package/
info :   Forbidden https://www.nuget.org/api/v2/package/ 1398 ms
error: Response status code does not indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).

I discovered it using the web gallery instead of command line.

A meaningful message after this kind of fail for dotnet pack will be very useful!

Thank you for excellent job.

@karann-msft

This comment has been minimized.

Copy link
Contributor

@karann-msft karann-msft commented Jan 15, 2020

dotnet pack cannot predict what source you plan to push a package to. Are you saying you don't get the same error on dotnet nuget push?

@gsscoder

This comment has been minimized.

Copy link
Author

@gsscoder gsscoder commented Jan 16, 2020

Yes, exactly. NuGet gallery spotted the problem. When pushing using the command line, dotnet nuget push complained about API Key (saying it's expired or incorrect).

@karann-msft

This comment has been minimized.

Copy link
Contributor

@karann-msft karann-msft commented Jan 16, 2020

"or does not have permission to access the specified package." which is kinda the case here.

@gsscoder

This comment has been minimized.

Copy link
Author

@gsscoder gsscoder commented Jan 17, 2020

Ok.
It was just to let you know if it's the case to change something, but after all I think it's not a real problem.
Thank you

@gsscoder gsscoder closed this Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.