1 |
Neil Bothwick wrote: |
2 |
> On Thu, 04 Jun 2020 21:24:39 +0000, Caveman Al Toraboran wrote: |
3 |
> |
4 |
>> if i exec: "emerge -avDuNt --quiet-build=y @world": |
5 |
>> |
6 |
>> > These are the packages that would be merged, in reverse order: |
7 |
>> > |
8 |
>> > Calculating dependencies... done! |
9 |
>> > |
10 |
>> > The following USE changes are necessary to proceed: |
11 |
>> > (see "package.use" in the portage(5) man page for more details) |
12 |
>> > # |
13 |
>> > >=dev-python/docutils-0.16 -python_targets_python2_7 |
14 |
>> > |
15 |
>> > Would you like to add these changes to your config files? |
16 |
>> > [Yes/No] |
17 |
>> |
18 |
>> so >=dev-python/docutils-0.16 doesn't want |
19 |
>> python_targets_python2_7. let's remove it then by |
20 |
>> adding: |
21 |
>> |
22 |
>> >=dev-python/docutils-0.16 -python_targets_python2_7 |
23 |
>> |
24 |
>> into: /etc/portage/package.use/stuff |
25 |
>> |
26 |
>> but then i get this: |
27 |
>> |
28 |
>> > The following USE changes are necessary to proceed: |
29 |
>> > (see "package.use" in the portage(5) man page for more details) |
30 |
>> > # required by dev-python/m2r-0.2.1::gentoo[-test] |
31 |
>> > # required by dev-python/automat-20.2.0::gentoo |
32 |
>> > # required by dev-python/twisted-20.3.0::gentoo |
33 |
>> > # required by www-servers/tornado-6.0.4::gentoo |
34 |
>> > # required by dev-python/ipykernel-5.1.4::gentoo[-test] |
35 |
>> > # required by dev-python/ipyparallel-6.2.3::gentoo |
36 |
>> > # required by dev-python/ipython-7.5.0::gentoo[smp] |
37 |
>> > # required by @selected |
38 |
>> > # required by @world (argument) |
39 |
>> > >=dev-python/docutils-0.16 python_targets_python2_7 |
40 |
>> > |
41 |
>> > Would you like to add these changes to your config files? |
42 |
>> > [Yes/No] |
43 |
>> |
44 |
>> which i guess means that docutils wants py2.7. |
45 |
>> |
46 |
>> |
47 |
>> any idea how to handle this situation? |
48 |
> Allow portage to add the changes to your config, then run etc-update or |
49 |
> equivalent. When portage adds package.use changes, it also adds comments |
50 |
> showing what requires those changes. With that information, you should be |
51 |
> able to see which package is causing this. |
52 |
> |
53 |
> |
54 |
|
55 |
|
56 |
One of us is reading that wrong. Given my eyes, maybe it is me. My new |
57 |
glasses should be in within the next week or so. In the first instance, |
58 |
it wants py2.7 disabled. So he adds it to the config file to disable |
59 |
it. When he runs the command again, it wants to enable py2.7 for the |
60 |
same package and version. If I'm reading that right, even if he lets |
61 |
emerge add the change, it will lead to two problems. One, there will be |
62 |
one line enabling py2.7 and another line disabling it. If I recall |
63 |
correctly, emerge will take the last one. Two, he will be back to the |
64 |
first problem, it wanting py2.7 disabled. In other words, back where he |
65 |
started. |
66 |
|
67 |
Am I reading that wrong or something?? |
68 |
|
69 |
Dale |
70 |
|
71 |
:-) :-) |