What You Are Seeing?
When uninstalling a package where the id in lib\packageName.nuspec and the nuspec file inside lib\packageName.nupkg have different casing, the uninstallation process throws an error
reporting that the lib\PackageName path was not found.
It does not matter if the uninstall script is run, or if it is skipped.
What is Expected?
No error even if the casing is different
How Did You Get This To Happen? (Steps to Reproduce)
I'll give an example with the InnoSetup package.
The casing on the website uses upper case I and S, while when I pushed
the package with all lowercase.
When that package is then installed, the casing of the id element in the nuspec file inside the downloaded nupkg file and the nuspec file in the lib folder are different causing the error of a path not found.
Output Log
https://gist.github.com/AdmiringWorm/bac515b64b3d4e22f5eba385b07efb5c
Tested with choco versions
choco 0.10.3 (Error occurred)
choco 0.10.2 (Error occurred)
choco 0.10.1 (No Error)
What You Are Seeing?
When uninstalling a package where the id in
lib\packageName.nuspecand the nuspec file insidelib\packageName.nupkghave different casing, the uninstallation process throws an errorreporting that the
lib\PackageNamepath was not found.It does not matter if the uninstall script is run, or if it is skipped.
What is Expected?
No error even if the casing is different
How Did You Get This To Happen? (Steps to Reproduce)
I'll give an example with the InnoSetup package.
The casing on the website uses upper case I and S, while when I pushed
the package with all lowercase.
When that package is then installed, the casing of the id element in the nuspec file inside the downloaded nupkg file and the nuspec file in the lib folder are different causing the error of a path not found.
Output Log
https://gist.github.com/AdmiringWorm/bac515b64b3d4e22f5eba385b07efb5c
Tested with choco versions
choco 0.10.3 (Error occurred)
choco 0.10.2 (Error occurred)
choco 0.10.1 (No Error)