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 performing an upgrade of a package, files that are created during the installation/usage of the software that the package installs, and placed into the package lib folder, are not present during the upgrade of the package.
For example, let's say you have a package that during installation, creates a file in the lib folder to store "stuff". This could be configuration information for example. During an upgrade, you may want to use the information in this file, to do other "stuff". However, this file that was placed there during installation, or after installation, isn't present in the lib folder during the upgrade.
What is Expected?
Any files that are added to the lib folder during installation, or after, should be present in the lib folder during installation. This is how things worked in 1.x of Chocolatey CLI.
See the testing steps below for more information on this regression.
How Did You Get This To Happen?
Run the following commands in 1.x and 2.x of Chocolatey CLI, and you should get the following results:
Notice that the "The file doesn't exist, but it likely should..." message appears both during install and upgrade when run through 2.x, but only appears once when installed via 1.x.
Checklist
What You Are Seeing?
When performing an upgrade of a package, files that are created during the installation/usage of the software that the package installs, and placed into the package lib folder, are not present during the upgrade of the package.
For example, let's say you have a package that during installation, creates a file in the lib folder to store "stuff". This could be configuration information for example. During an upgrade, you may want to use the information in this file, to do other "stuff". However, this file that was placed there during installation, or after installation, isn't present in the lib folder during the upgrade.
What is Expected?
Any files that are added to the lib folder during installation, or after, should be present in the lib folder during installation. This is how things worked in 1.x of Chocolatey CLI.
See the testing steps below for more information on this regression.
How Did You Get This To Happen?
Run the following commands in 1.x and 2.x of Chocolatey CLI, and you should get the following results:
Notice that the "The file doesn't exist, but it likely should..." message appears both during install and upgrade when run through 2.x, but only appears once when installed via 1.x.
retain-package-files-on-upgrade.0.2.0.zip
retain-package-files-on-upgrade.0.1.0.zip
System Details
Installed Packages
Output Log
Additional Context
N/A
The text was updated successfully, but these errors were encountered: