1 |
On 03/17/2017 02:49 AM, Dale wrote: |
2 |
> Ralf wrote: |
3 |
>> On 03/17/2017 02:28 AM, Neil Bothwick wrote: |
4 |
>>> Read the message again, it needs one of python3_4 or python3_5 in |
5 |
>>> single target, you have neither. |
6 |
>> ... And read mine :-) |
7 |
>> I know. |
8 |
>> And I know how I could fix that for single packages, but then the |
9 |
>> next package complains about the very same issues. So somehow |
10 |
>> 'default' settings seem not to apply any more. |
11 |
>>> |
12 |
>>> Do you have any PYTHON entries in make.conf? |
13 |
>> No, not yet. My profile: |
14 |
>> default/linux/amd64/13.0/desktop/gnome/systemd |
15 |
>> |
16 |
>> And I didn't do anything suspicious in the meanwhile, so for me it |
17 |
>> seems they changed something in the profile. |
18 |
>> |
19 |
>> Thanks |
20 |
>> Ralf |
21 |
>>> |
22 |
>>> On 17 March 2017 01:09:29 GMT+00:00, Ralf |
23 |
>>> <ralf+gentoo@×××××××××××××××××××.de> wrote: |
24 |
>>> |
25 |
>>> Hi, |
26 |
>>> |
27 |
>>> so I just emerged some unrelated packages, and then the following |
28 |
>>> happened when trying to update my system: |
29 |
>>> |
30 |
>>> !!! The ebuild selected to satisfy ">=app-editors/gedit-3.22.0" has |
31 |
>>> unmet requirements. |
32 |
>>> - app-editors/gedit-3.22.0::gentoo USE="introspection python spell -test |
33 |
>>> -vala" ABI_X86="64" PYTHON_SINGLE_TARGET="-python3_4 -python3_5" |
34 |
>>> PYTHON_TARGETS="python3_4 -python3_5" |
35 |
>>> |
36 |
>>> The following REQUIRED_USE flag constraints are unsatisfied: |
37 |
>>> python? ( exactly-one-of ( python_single_target_python3_4 |
38 |
>>> python_single_target_python3_5 ) ) |
39 |
>>> |
40 |
>>> The above constraints are a subset of the following complete expression: |
41 |
>>> python? ( introspection exactly-one-of ( |
42 |
>>> python_single_target_python3_4 python_single_target_python3_5 ) |
43 |
>>> python_single_target_python3_4? ( python_targets_python3_4 ) |
44 |
>>> python_single_target_python3_5? ( python_targets_python3_5 ) ) |
45 |
>>> |
46 |
>>> |
47 |
>>> So somehow PYTHON_TARGET and PYTHON_SINGLETARGET got screwed on my |
48 |
>>> system. I know how I could fix this for gedit only, but then other |
49 |
>>> packages begin complaining about the same issue as well. |
50 |
>>> |
51 |
>>> Anything helps! |
52 |
>>> |
53 |
>>> Cheers |
54 |
>>> Ralf |
55 |
>>> |
56 |
>>> |
57 |
>>> -- |
58 |
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. |
59 |
>> |
60 |
>> |
61 |
> |
62 |
> |
63 |
> I would check emerge --info just to confirm it. If that shows a wrong |
64 |
> setting, then you know it is a setting, somewhere. If it doesn't, |
65 |
> whole new can of worms. |
66 |
> |
67 |
> Dale |
68 |
> |
69 |
> :-) :-) |
70 |
|
71 |
It tells me: |
72 |
PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" |
73 |
|
74 |
So that's what I guess, that it's a setting somewhere... But where? |
75 |
Everything used to work before. |
76 |
|
77 |
Ralf |