When installing or upgrading packages with dependencies, the error 'Unable to resolve dependency' is encountered

**(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):

1. 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)._

There are a couple of options available:

1. Read the [dependency documentation and work through the examples](https://docs.chocolatey.org/en-us/choco/troubleshooting/dependency-troubles).
2. Watch the [YouTube video](https://www.youtube.com/live/mulMztVQzQU?si=B1HKCSsJJMmfdg11&t=1208) where we take you through some common scenarios and solutions.
3. Reach out on our [Community Hub](https://ch0.co/community).

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

* #3495
* #3493
* #3487
* #3481
* #3480
* #3366
* #3349
* #3346
* #3323
* #3314
* #3300
* #3234
* #3227
* #3226
* #3199
* #3176

Start with the linked dependency documentation, video, and related issues to identify the scenarios and guidance already covered. Expand the troubleshooting information with verified examples and keep the resolution paths consistent; done when the common dependency cases and next steps are documented without requiring a new issue for clarification.

Written by the indexing model from the issue text.