[email protected] wrote:
> On 12/10 01:37, Jack wrote:
>> On 2019.12.09 22:22, [email protected] wrote:
>>> Hi,
>>>
>>> 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.)
>>>
>>> Cheers!
>>> mcc
>> 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?
>>
>> Jack
> Hi Jack,
>
> 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 don't know if this is the problem or not but it may be worth looking
into the python 2.7 target requirement. The devs are actively removing
python 2.7 support since it is reaching its end of life. It could
possibly be causing this problem but even if it isn't, you need to
prepare for python 2.7 to be gone.
Additional note, you may use a script or something so this may not
matter. Some of the options/settings you use can be set in make.conf.
Examples from my make.conf:
PORTAGE_NICENESS=5
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}"
FEATURES="-usersync userpriv usersandbox buildpkg sandbox parallel-fetch"
MAKEOPTS="-j9"
EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5
--quiet-build=n -1 --unordered-display"
Having default settings in make.conf saves you from having to remember
them all since it uses them automatically. Just a thought.
Hope that helps.
Dale
:-) :-)
