tu...@posteo.de wrote: > On 12/11 05:55, Neil Bothwick wrote: >> On Wed, 11 Dec 2019 12:49:01 -0500, Jack wrote: >> >>>> package.use/inkscape:media-gfx/inkscape jpeg nls openmp cdr dbus dia >>>> exif -gnome imagemagick inkjar latex lcms postscript visio wpg >>>> PYTHON_TARGETS="python2_7") >>>> >>>> >>>> Cheers! >>>> mcc >>> I'm curious why you have the PYTHON_TARGET set for imagemagick. I >>> don't see any mention of python anywhere in any of the imagemagick >>> ebuilds, and "emerge -p imagemagick" doesn't say anything about python. >> He doesn't, it is set for inkscape. However, that trailing ) shouldn't be >> there. I doubt it is the cause of the problem, but it's worth cleaning up >> anyway. >> >> >> -- >> Neil Bothwick >> >> WinErr 683: Time out error - Operator fell asleep while waiting for the >> system to complete boot procedure. > I removed the ')' and updated again (did this aboyt 2h before). > > The onlu one, which ich being emerged is imagemagick... > > But I saw this again: > > WARNING: One or more updates/rebuilds have been skipped due to a dependency > conflict: > > media-gfx/imagemagick:0 > > (media-gfx/imagemagick-7.0.9.7:0/7.0.9::gentoo, ebuild scheduled for merge) > conflicts with > <media-gfx/imagemagick-7:0/6.9.10.77=[cxx] required by > (media-gfx/inkscape-1.0_beta2:0/0::gentoo, installed) > ^ ^^^^^^^^^^^^^ > <media-gfx/imagemagick-7:=[cxx] required by > (media-gfx/inkscape-1.0_beta2:0/0::gentoo, installed) > ^ ^ > > Cheers! > mcc >
I vaguely remember seeing this. I couldn't recall the fix so I went digging. I found this: /etc/portage/package.use/package.use:media-gfx/imagemagick cxx It seems I added the cxx USE flag for that package to correct the problem. Might be worth a try. Hope that helps. Dale :-) :-)
