On 12/06/2016 12:50, Heiko Baums wrote:
Am 12.06.2016 um 12:05 schrieb Alan McKinnon:
My main desktop has been giving me these stupid error for a week now.
ANd I can't figure out what portage wants to do or how to stop it (other
than masking graphics magick):
[blocks B ] media-gfx/graphicsmagick[imagemagick]
("media-gfx/graphicsmagick[imagemagick]" is blocking
media-gfx/imagemagick-6.9.4.7)
[blocks B ] media-gfx/imagemagick ("media-gfx/imagemagick" is
blocking media-gfx/graphicsmagick-1.3.24)
So here's the question: Why is portage not realising I already have a
suitable *magick and decides I ought to have the blocker?
Install graphicsmagick with USE="-imagemagick".
If I recall correctly the blocker is because of a file or a feature
collision of media-gfx/imagemagick and
media-gfx/graphicsmagick[imagemagick].
I could do that, but I don't see any compelling reason to have
graphicsmagick at all and I can't figure why portage doesn't accept
installed imagemagick as fulfilling the DEPEND
As per my other reply to Neil, --changed-deps=n makes a difference
emerge --changed-deps=y finds graphicsmagick and wants to use it
emerge --changed-deps=n finds imagemagick and uses that.
Maybe if I set --backtrack=<some_insane_high_number> portage will find a
resolution.
Alan
