Closed gep13 closed 7 months ago
Workaround
A suggested workaround while this problem is worked on would be to use the --skip-download-cache
option, to bypass the usage of the Chocolatey CDN.
i.e.
choco download GoogleChrome --internalize --source https://community.chocolatey.org/api/v2/ --skip-download-cache
The issue related to this has been resolved and deployed.
Some existing packages may still exhibit this behavior for some time. Please reach out to us in discord, or comment here on this issue with the package ID and Version, and we can resolve it immediately.
Thank you for getting this issue resolved. I was able to successfully internalize the GoogleChrome package. Really appreciate the help!
Checklist
What You Are Seeing?
When attempting to download (also known an internalize) a package from the Chocolatey Community Repository, the following error is returned:
What is Expected?
The internalization process should succeed without error.
How Did You Get This To Happen?
Execute the following command:
Since this package uses an installer which is cached in the Chocolatey CDN, it will attempt to download the application installer from there, and it will fail to find it, even those it is there.
That is why the 403 error is generated.
System Details
Installed Packages
Output Log
Additional Context
The underlying problem here is a change to the Chocolatey Community Repository which was detailed in our blog post.
One of the changes that was made here was to change how we address Package IDs, and this has had an unintended consequence of breaking how the download URL for application installers is done against the Chocolatey CDN.
┆Issue is synchronized with this Gitlab issue by Unito