You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified this is the correct repository for opening this issue.
I have verified no other issues exist related to my problem.
I have verified this is not an issue for a specific package.
I have verified this issue is not security related.
I confirm I am using official, and not unofficial, or modified, Chocolatey products.
What You Are Seeing?
When a package exists in the lib folder, but does not have any corresponding entries in the .chocolatey folder, the error 'Not a valid nupkg file' is shown. This stops Chocolatey CLI from doing anything else until the problem is resolved.
What is Expected?
If there is a problem with a particular package, Chocolatey CLI should warn the user, but should still function. If possible, it should let the user know what they should do and what the error is (i.e., no equivalent package ID in .chocolatey folder for example).
How Did You Get This To Happen?
See the Zendesk ticket for more information. Note that there is also a script that was created to resolve the problem in that ticket.
Checklist
What You Are Seeing?
When a package exists in the
lib
folder, but does not have any corresponding entries in the.chocolatey
folder, the error 'Not a valid nupkg file' is shown. This stops Chocolatey CLI from doing anything else until the problem is resolved.What is Expected?
If there is a problem with a particular package, Chocolatey CLI should warn the user, but should still function. If possible, it should let the user know what they should do and what the error is (i.e., no equivalent package ID in
.chocolatey
folder for example).How Did You Get This To Happen?
See the Zendesk ticket for more information. Note that there is also a script that was created to resolve the problem in that ticket.
System Details
N/A
Installed Packages
N/A
Output Log
See the Zendesk ticket for more information.
Additional Context
This is related to a Zendesk ticket.
The text was updated successfully, but these errors were encountered: