1 |
Fernando Rodriguez schrieb: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA256 |
4 |
> |
5 |
> On 08/13/2016 09:40 AM, hw wrote: |
6 |
>> Fernando Rodriguez schrieb: |
7 |
>>> -----BEGIN PGP SIGNED MESSAGE----- |
8 |
>>> Hash: SHA256 |
9 |
>>> |
10 |
>>> On 08/12/2016 08:44 AM, Jeroen Mathon wrote: |
11 |
>>>> Is it perhaps an idea to mask the gentoolkit package when updating portage? |
12 |
>>> |
13 |
>>> Since that version of gentoolkit doesn't depend on a specific version of portage |
14 |
>>> but does depend on portage with the same python_targets use flags, I think the problem |
15 |
>>> is that you're trying to emerge portage and gentoolkit with different python_target_XXX |
16 |
>>> flags, So just make sure they're the same. |
17 |
>> |
18 |
>> I have removed gentoolkit, and it still fails: |
19 |
>> |
20 |
>> emerge --ask --update --newuse portage |
21 |
>> [...] |
22 |
>> WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: |
23 |
>> |
24 |
>> sys-apps/portage:0 |
25 |
>> |
26 |
>> (sys-apps/portage-2.2.28:0/0::gentoo, ebuild scheduled for merge) conflicts with |
27 |
>> sys-apps/portage[python_targets_python2_7(-),python_targets_python3_3(-),-python_single_target_python2_7(-),-python_single_target_python3_3(-)] required by (app-admin/webapp-config-1.52-r1:0/0::gentoo, installed) |
28 |
>> |
29 |
>> |
30 |
> |
31 |
> Now it's app-admin/webapp-config it has the same dep on portage (sys-apps/portage[${PYTHON_USEDEP}]) only when the portage use flag is enabled. |
32 |
> |
33 |
> You're trying to build portage with a new python target when everything else is built for a different |
34 |
> python version. Either change portage's to the same as everythhing else or remerge all packages that depend |
35 |
> on portage first. |
36 |
|
37 |
Since someone said I should use the same python target for everything, |
38 |
I set one globally. Why wouldn´t that target be used? |
39 |
|
40 |
Even if that would work, I can´t update portage before it´s updated to |
41 |
a version which can work with EAPI 6 packages, and it can´t be updated |
42 |
before it can work with EAPI 6 packages. |
43 |
|
44 |
So the only way to update would be step by step. I´m probably willing |
45 |
to try that, but I expect other problems when doing that, like with |
46 |
updating perl. And I can´t do that because it is required that perl |
47 |
works when the updating is done. |