On 2019.12.10 23:09, [email protected] wrote:
On 12/10 01:37, Jack wrote:
> On 2019.12.09 22:22, [email protected] wrote:
> > it seems, there is an installation loop for
> > Installing (2 of 2) media-gfx/imagemagick-6.9.10.77::gentoo
. Nearly every morning since some days I see this. What may cause
the problem? (It installas just fine.)
> >
My portage shows that 6.9.10.77 is ~ but 7.0.9.5 is stable. Do you
have any package.x entries which might affect which version can be
installed? No, I have no idea why that would make it reinstall the
same version daily, but it might be a starting point. Also, which
emerge command is producing that result? Is the other package (1 of
2) always the same, or does that vary by day?
this command is used for updateing:
ionice -c 3 -n 7 nice -n 5 eix-sync ;ionice -c 3 -n 7 nice -n 5
emerge --update --newuse --deep --with-bdeps=n --tree --keep-going
--backtrack=30 -v --verbose-conflicts -1 @world
when this has done its job, this comand is used to clean up:
emerge --selective=n @preserved-rebuild && emerge --depclean -va &&
eclean-dist -C -d -v && eix-test-obsolete
In the past, this has worked fine for me (I am using 'unstable')
The last actions related to imagemagick were (qlop -m -u -v) :
2019-11-20T05:00:52 >>> media-gfx/imagemagick-6.9.10.73
2019-11-20T17:43:50 >>> media-gfx/imagemagick-6.9.10.73
2019-11-21T03:59:33 >>> media-gfx/imagemagick-6.9.10.73
2019-11-21T18:06:49 >>> media-gfx/imagemagick-6.9.10.73
2019-11-22T03:47:45 >>> media-gfx/imagemagick-6.9.10.73
2019-11-22T17:21:54 >>> media-gfx/imagemagick-6.9.10.73
2019-11-23T04:00:34 >>> media-gfx/imagemagick-6.9.10.73
2019-12-03T17:17:58 >>> media-gfx/imagemagick-6.9.10.77
2019-12-04T03:12:26 >>> media-gfx/imagemagick-6.9.10.77
2019-12-04T17:30:03 >>> media-gfx/imagemagick-6.9.10.77
2019-12-05T04:42:22 >>> media-gfx/imagemagick-6.9.10.77
2019-12-05T17:44:49 >>> media-gfx/imagemagick-6.9.10.77
2019-12-06T02:58:10 >>> media-gfx/imagemagick-6.9.10.77
2019-12-06T17:39:24 >>> media-gfx/imagemagick-6.9.10.77
2019-12-07T01:11:23 >>> media-gfx/imagemagick-6.9.10.77
2019-12-07T04:25:47 >>> media-gfx/imagemagick-6.9.10.77
2019-12-07T16:55:51 >>> media-gfx/imagemagick-7.0.9.7
2019-12-08T04:33:29 >>> media-gfx/imagemagick-6.9.10.77
2019-12-09T04:29:51 >>> media-gfx/imagemagick-6.9.10.77
2019-12-09T17:38:44 >>> media-gfx/imagemagick-6.9.10.77
2019-12-10T03:59:49 >>> media-gfx/imagemagick-6.9.10.77
2019-12-10T17:26:51 >>> media-gfx/imagemagick-6.9.10.77
2019-12-11T03:43:13 >>> media-gfx/imagemagick-6.9.10.77
The "other" packages differ with each update.
There are no package.x-entries (related to or nameing imagemagick)
other than this one:
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.
Something does seem funny, though, since you did upgrade to 7.0.9.7 for
one day, and then back to the previous version. "equery d imagemagick"
only shows me emacs and pillow, and neither specifies a specific
version, but grepping through all ebuilds for imagemagick does show
many others which seem to depend on it. I wonder if something else you
have installed might be requiring a specific version. What do you get
for "equery d imagemagick" and "emerge -pc imagemagick"?
Jack
