On 12/06/2016 12:13, Neil Bothwick wrote:
On Sun, 12 Jun 2016 12:05:47 +0200, Alan McKinnon wrote:
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)
graphicsmagick is not installed.
Everything pulling in graphicsmagick is already satisfied by
imagemagick[png]:
So here's the question: Why is portage not realising I already have a
suitable *magick and decides I ought to have the blocker?
You've probably already tried these but
does adding --tree give anything more useful?
Not really. The depgraph in the error output covers it all
Does grep magick -r /etc/portage show anything?
No,
# grep -r magick /etc/portage/
/etc/portage/make.conf: -icq icu id3tag ieee1394 imagemagick imap
innodb introspection \
/etc/portage/package.use/package.use:media-gfx/imagemagick fpx hdri q32 q8
/etc/portage/package.use/libperl:media-gfx/imagemagick -perl
I *did* have --changed-deps=y in my emerge world command, taking it out
works and portage does what I expect. I read the man page entry for it, but
a) it doesn't make much sense
b) I can't see how that would make a difference
