1 |
tuxic@××××××.de wrote: |
2 |
> On 12/10 01:37, Jack wrote: |
3 |
>> On 2019.12.09 22:22, tuxic@××××××.de wrote: |
4 |
>>> Hi, |
5 |
>>> |
6 |
>>> it seems, there is an installation loop for |
7 |
>>> |
8 |
>>> Installing (2 of 2) media-gfx/imagemagick-6.9.10.77::gentoo |
9 |
>>> |
10 |
>>> . Nearly every morning since some days I see this. |
11 |
>>> What may cause the problem? (It installas just fine.) |
12 |
>>> |
13 |
>>> Cheers! |
14 |
>>> mcc |
15 |
>> My portage shows that 6.9.10.77 is ~ but 7.0.9.5 is stable. Do you have any |
16 |
>> package.x entries which might affect which version can be installed? No, I |
17 |
>> have no idea why that would make it reinstall the same version daily, but it |
18 |
>> might be a starting point. Also, which emerge command is producing that |
19 |
>> result? Is the other package (1 of 2) always the same, or does that vary by |
20 |
>> day? |
21 |
>> |
22 |
>> Jack |
23 |
> Hi Jack, |
24 |
> |
25 |
> this command is used for updateing: |
26 |
> 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 |
27 |
> |
28 |
> when this has done its job, this comand is used to clean up: |
29 |
> emerge --selective=n @preserved-rebuild && emerge --depclean -va && eclean-dist -C -d -v && eix-test-obsolete |
30 |
> |
31 |
> In the past, this has worked fine for me (I am using 'unstable') |
32 |
> |
33 |
> The last actions related to imagemagick were (qlop -m -u -v) : |
34 |
> 2019-11-20T05:00:52 >>> media-gfx/imagemagick-6.9.10.73 |
35 |
> 2019-11-20T17:43:50 >>> media-gfx/imagemagick-6.9.10.73 |
36 |
> 2019-11-21T03:59:33 >>> media-gfx/imagemagick-6.9.10.73 |
37 |
> 2019-11-21T18:06:49 >>> media-gfx/imagemagick-6.9.10.73 |
38 |
> 2019-11-22T03:47:45 >>> media-gfx/imagemagick-6.9.10.73 |
39 |
> 2019-11-22T17:21:54 >>> media-gfx/imagemagick-6.9.10.73 |
40 |
> 2019-11-23T04:00:34 >>> media-gfx/imagemagick-6.9.10.73 |
41 |
> 2019-12-03T17:17:58 >>> media-gfx/imagemagick-6.9.10.77 |
42 |
> 2019-12-04T03:12:26 >>> media-gfx/imagemagick-6.9.10.77 |
43 |
> 2019-12-04T17:30:03 >>> media-gfx/imagemagick-6.9.10.77 |
44 |
> 2019-12-05T04:42:22 >>> media-gfx/imagemagick-6.9.10.77 |
45 |
> 2019-12-05T17:44:49 >>> media-gfx/imagemagick-6.9.10.77 |
46 |
> 2019-12-06T02:58:10 >>> media-gfx/imagemagick-6.9.10.77 |
47 |
> 2019-12-06T17:39:24 >>> media-gfx/imagemagick-6.9.10.77 |
48 |
> 2019-12-07T01:11:23 >>> media-gfx/imagemagick-6.9.10.77 |
49 |
> 2019-12-07T04:25:47 >>> media-gfx/imagemagick-6.9.10.77 |
50 |
> 2019-12-07T16:55:51 >>> media-gfx/imagemagick-7.0.9.7 |
51 |
> 2019-12-08T04:33:29 >>> media-gfx/imagemagick-6.9.10.77 |
52 |
> 2019-12-09T04:29:51 >>> media-gfx/imagemagick-6.9.10.77 |
53 |
> 2019-12-09T17:38:44 >>> media-gfx/imagemagick-6.9.10.77 |
54 |
> 2019-12-10T03:59:49 >>> media-gfx/imagemagick-6.9.10.77 |
55 |
> 2019-12-10T17:26:51 >>> media-gfx/imagemagick-6.9.10.77 |
56 |
> 2019-12-11T03:43:13 >>> media-gfx/imagemagick-6.9.10.77 |
57 |
> |
58 |
> The "other" packages differ with each update. |
59 |
> |
60 |
> There are no package.x-entries (related to or nameing imagemagick) other than this one: |
61 |
> 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") |
62 |
> |
63 |
> |
64 |
> Cheers! |
65 |
> mcc |
66 |
> |
67 |
> |
68 |
|
69 |
|
70 |
I don't know if this is the problem or not but it may be worth looking |
71 |
into the python 2.7 target requirement. The devs are actively removing |
72 |
python 2.7 support since it is reaching its end of life. It could |
73 |
possibly be causing this problem but even if it isn't, you need to |
74 |
prepare for python 2.7 to be gone. |
75 |
|
76 |
Additional note, you may use a script or something so this may not |
77 |
matter. Some of the options/settings you use can be set in make.conf. |
78 |
Examples from my make.conf: |
79 |
|
80 |
|
81 |
PORTAGE_NICENESS=5 |
82 |
PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
83 |
FEATURES="-usersync userpriv usersandbox buildpkg sandbox parallel-fetch" |
84 |
MAKEOPTS="-j9" |
85 |
EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5 |
86 |
--quiet-build=n -1 --unordered-display" |
87 |
|
88 |
|
89 |
Having default settings in make.conf saves you from having to remember |
90 |
them all since it uses them automatically. Just a thought. |
91 |
|
92 |
Hope that helps. |
93 |
|
94 |
Dale |
95 |
|
96 |
:-) :-) |