1 |
On Wed, Nov 29 2017, Alan McKinnon wrote: |
2 |
|
3 |
> On 29/11/2017 21:48, allan gottlieb wrote: |
4 |
>> I have two systems that are close in both hardware and software. |
5 |
>> |
6 |
>> Today I did eix-sync on each followed by |
7 |
>> emerge --update --changed-use --with-bdeps=y @world |
8 |
>> |
9 |
>> On one system (dell 6430) I was presented with many packages to merge |
10 |
>> python-3.5.4 [ebuild NS] |
11 |
>> many to reinstall [ebuild R] |
12 |
>> |
13 |
>> This was not surprising. |
14 |
>> |
15 |
>> The other system (dell 7450) failed with the following |
16 |
>> |
17 |
>> !!! Problem resolving dependencies for sys-process/systemd-cron from @selected |
18 |
>> ... done! |
19 |
>> |
20 |
>> !!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements. |
21 |
>> - sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)" |
22 |
>> |
23 |
>> The following REQUIRED_USE flag constraints are unsatisfied: |
24 |
>> exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 ) |
25 |
>> |
26 |
>> The above constraints are a subset of the following complete expression: |
27 |
>> exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 ) |
28 |
>> |
29 |
>> (dependency required by "@selected" [set]) |
30 |
>> (dependency required by "@world" [argument]) |
31 |
>> |
32 |
>> Both 6430 and 7450 have the following content in |
33 |
>> /etc/portage/package.use/systemd-cron |
34 |
>> |
35 |
>> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x. |
36 |
>> sys-process/systemd-cron python_single_target_python3_4 |
37 |
>> |
38 |
>> Those files are 2+ years old on each system |
39 |
>> |
40 |
>> I have not let the 6430 proceed with the emerge update world. |
41 |
>> |
42 |
>> Thanks in advance for any help. |
43 |
>> allan |
44 |
>> |
45 |
> |
46 |
> Your machines differ between PYTHON_TARGETS and PYTHON_SINGLE_TARGET, |
47 |
> either globally or for that one package. Compare: |
48 |
> |
49 |
> emerge --info | grep PYTHON |
50 |
> list of installed pythons |
51 |
> eselect python list |
52 |
> |
53 |
> The cause is likely in make.conf somewhere |
54 |
|
55 |
Thanks for the help, but I still have the problem. |
56 |
|
57 |
emerge --info showed the same for PYTHON_SINGLE_TARGET="python3_5" and |
58 |
PYTHON_TARGETS="python2_7 python3_5" |
59 |
|
60 |
eix -I python shows 2.7.14 and 3.4.5 on both systems |
61 |
|
62 |
grep -i python /etc/portage/make.conf |
63 |
has no hits on either system |
64 |
|
65 |
eselect python list showed the same two version (3.4 and 2.7) |
66 |
but in *opposite* order. I issued |
67 |
eselect python set 2 |
68 |
on the failing 7450 and now both report |
69 |
Available Python interpreters, in order of preference: |
70 |
[1] python3.4 |
71 |
[2] python2.7 |
72 |
|
73 |
I don't believe I need to "activate" this change, right? |
74 |
|
75 |
However, after making the above change the 7450 still fails to emerge |
76 |
update world saying |
77 |
|
78 |
Calculating dependencies - |
79 |
|
80 |
!!! Problem resolving dependencies for sys-process/systemd-cron from @selected |
81 |
... done! |
82 |
|
83 |
!!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements. |
84 |
- sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)" |
85 |
|
86 |
The following REQUIRED_USE flag constraints are unsatisfied: |
87 |
exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 ) |
88 |
|
89 |
The above constraints are a subset of the following complete expression: |
90 |
exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 ) |
91 |
|
92 |
(dependency required by "@selected" [set]) |
93 |
(dependency required by "@world" [argument]) |