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
(NOTE: This is a work in progress that we will continue to update).
This issue has been created to provide additional information on how to resolve dependency issues and to collect these dependency issues together.
When installing or upgrading a package, you may see the error:
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'PACKAGE 3.11.4 constraint: PACKAGE (= 3.11.4)'
Unable to resolve dependency 'PACKAGE'. Source(s) used: 'SOURCE'.
(Note PACKAGE and SOURCE can be any package or source and are being used as examples).
There are a few common scenarios we have seen that can lead to this (in no particular order):
You have a meta-package (emacs for example) that depends on another package (emacs.install). The other package (emacs.install) has been uninstalled by some means. This would break the dependency for the meta-package (emacs).
(NOTE: The above list is a work in progress that we will continue to add to).
Please do not raise an issue on this until you have gone through the options above and the Chocolatey Team requests you to. If you do raise an issue before doing the above, it is highly likely it will be closed.
pauby
changed the title
When installing or upgrading packages with dependencies, the error 'Unable to resolve dependency' is given
When installing or upgrading packages with dependencies, the error 'Unable to resolve dependency' is encountered
Aug 7, 2024
(NOTE: This is a work in progress that we will continue to update).
This issue has been created to provide additional information on how to resolve dependency issues and to collect these dependency issues together.
When installing or upgrading a package, you may see the error:
(Note
PACKAGE
andSOURCE
can be any package or source and are being used as examples).There are a few common scenarios we have seen that can lead to this (in no particular order):
emacs
for example) that depends on another package (emacs.install
). The other package (emacs.install
) has been uninstalled by some means. This would break the dependency for the meta-package (emacs
).(NOTE: The above list is a work in progress that we will continue to add to).
There are a couple of options available:
Please do not raise an issue on this until you have gone through the options above and the Chocolatey Team requests you to. If you do raise an issue before doing the above, it is highly likely it will be closed.
Related Issues
'vcredist140 14.40.33810' is not compatible with 'missionplanner 1.3.81 constraint: vcredist140 (>= 14.30.30704)'
does not seem logical #3495The text was updated successfully, but these errors were encountered: