| 1 |
On 12/06/2016 12:50, Heiko Baums wrote: |
| 2 |
> Am 12.06.2016 um 12:05 schrieb Alan McKinnon: |
| 3 |
>> My main desktop has been giving me these stupid error for a week now. |
| 4 |
>> ANd I can't figure out what portage wants to do or how to stop it (other |
| 5 |
>> than masking graphics magick): |
| 6 |
>> |
| 7 |
>> [blocks B ] media-gfx/graphicsmagick[imagemagick] |
| 8 |
>> ("media-gfx/graphicsmagick[imagemagick]" is blocking |
| 9 |
>> media-gfx/imagemagick-6.9.4.7) |
| 10 |
>> [blocks B ] media-gfx/imagemagick ("media-gfx/imagemagick" is |
| 11 |
>> blocking media-gfx/graphicsmagick-1.3.24) |
| 12 |
> |
| 13 |
>> So here's the question: Why is portage not realising I already have a |
| 14 |
>> suitable *magick and decides I ought to have the blocker? |
| 15 |
> |
| 16 |
> Install graphicsmagick with USE="-imagemagick". |
| 17 |
> |
| 18 |
> If I recall correctly the blocker is because of a file or a feature |
| 19 |
> collision of media-gfx/imagemagick and |
| 20 |
> media-gfx/graphicsmagick[imagemagick]. |
| 21 |
> |
| 22 |
|
| 23 |
|
| 24 |
I could do that, but I don't see any compelling reason to have |
| 25 |
graphicsmagick at all and I can't figure why portage doesn't accept |
| 26 |
installed imagemagick as fulfilling the DEPEND |
| 27 |
|
| 28 |
As per my other reply to Neil, --changed-deps=n makes a difference |
| 29 |
|
| 30 |
emerge --changed-deps=y finds graphicsmagick and wants to use it |
| 31 |
emerge --changed-deps=n finds imagemagick and uses that. |
| 32 |
|
| 33 |
Maybe if I set --backtrack=<some_insane_high_number> portage will find a |
| 34 |
resolution. |
| 35 |
|
| 36 |
Alan |
Archives