| 1 |
On 6/18/21 6:01 PM, Zac Medico wrote: |
| 2 |
> If emerge --depclean fails to resolve any dependencies, then it will |
| 3 |
> now suggest emerge @unsatisfied-deps as the simplest possible |
| 4 |
> solution, and will also suggest to unmerge @unavailable where |
| 5 |
> appropriate at the end: |
| 6 |
> |
| 7 |
> $ emerge --depclean |
| 8 |
> |
| 9 |
> Calculating dependencies... done! |
| 10 |
> * Dependencies could not be completely resolved due to |
| 11 |
> * the following required packages not being installed: |
| 12 |
> * |
| 13 |
> * virtual/cdrtools pulled in by: |
| 14 |
> * app-cdr/cdrdao-1.2.4 |
| 15 |
> * |
| 16 |
> * Have you forgotten to resolve unsatisfied dependencies prior to |
| 17 |
> * depclean? The simplest possible command for this purpose is as |
| 18 |
> * follows: |
| 19 |
> * |
| 20 |
> * emerge @unsatisfied-deps |
| 21 |
|
| 22 |
It turns out that @unsatisfied-deps is often unsuitable here because it |
| 23 |
pulls in a bunch of @installed packages, when you really want to use |
| 24 |
@world as the source of truth. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives