-
Notifications
You must be signed in to change notification settings - Fork 908
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
Do not install packages if dependencies fail to install #3487
Comments
When a package dependency fails to install, we will now fail the package as well.
Some of these package already existed on our internal repository, while some of them have been added for the tests being added.
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
When a package dependency fails to install, we will now fail the package as well.
Some of these package already existed on our internal repository, while some of them have been added for the tests being added.
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
When a package dependency fails to install, we will now fail the package as well.
Some of these package already existed on our internal repository, while some of them have been added for the tests being added.
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
I have also experienced this issue when installing/upgrading a package with
After that packages that are completely unrelated fail to install with:
|
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
Address review comments by using full version string for PackageResults, and use case insensitive compares when determining if a package has dependencies that failed to install.
When a package dependency fails to install, we will now fail the package as well.
Some of these package already existed on our internal repository, while some of them have been added for the tests being added.
We have added some tests for the install all command. This adds a new package source to the testing environment so that we can run the tests locally and in Test Kitchen.
Add a number of tests for dependency scenarios where we did not have tests before.
Address review comments by using full version string for PackageResults, and use case insensitive compares when determining if a package has dependencies that failed to install.
🎉 This issue has been resolved in version 2.4.0 🎉 The release is available on: |
Checklist
What You Are Seeing?
When a dependency fails to install, the failure does not prevent other packages which depend on it from installing.
What is Expected?
Failing to install a dependency should not permit anything that depends on it to still install.
How Did You Get This To Happen?
C:\packages
choco upgrade rootpackageA rootpackageB -y -s c:\packages
rootpackageB
despite it not actually depending on the failing dependencynested-dependencyA-failing
, androotpackageA
is permitted to install, despite this placing Chocolatey in a broken state where you cannot install any more packages until you rip out all the installed packages further up in the dependency chain.System Details
Installed Packages
N/A, this reproduces purely with the given test packages.
Output Log
Additional Context
No response
The text was updated successfully, but these errors were encountered: