1 |
On Saturday, 23 June 2018 12:35:32 BST you wrote: |
2 |
> On Saturday, 23 June 2018 11:09:10 BST Alec Ten Harmsel wrote: |
3 |
> > On Sat, Jun 23, 2018 at 10:38:35AM +0100, Mick wrote: |
4 |
> > > On Saturday, 23 June 2018 10:30:09 BST Neil Bothwick wrote: |
5 |
> > > > On 23 June 2018 10:14:31 BST, Mick <michaelkintzios@×××××.com> wrote: |
6 |
> > > > >I came up to this today following a portage sync: |
7 |
> > > > > |
8 |
> > > > ># emerge -uaNDv world |
9 |
> > > > > |
10 |
> > > > > |
11 |
> > > > >These are the packages that would be merged, in order: |
12 |
> > > > > |
13 |
> > > > >Calculating dependencies / |
14 |
> > > > > |
15 |
> > > > >!!! Problem resolving dependencies for sys-devel/gdb from @selected |
16 |
> > > > >.. done! |
17 |
> > > > > |
18 |
> > > > > |
19 |
> > > > >!!! The ebuild selected to satisfy "sys-devel/gdb" has unmet |
20 |
> > > > >requirements. |
21 |
> > > > >- sys-devel/gdb-7.12.1::gentoo USE="client nls python server xml |
22 |
> > > > >-lzma |
23 |
> > > > >- |
24 |
> > > > >multitarget -test -vanilla" ABI_X86="(64)" |
25 |
> > > > >PYTHON_SINGLE_TARGET="-python2_7 - |
26 |
> > > > >python3_4 -python3_5" PYTHON_TARGETS="python2_7 -python3_4 |
27 |
> > > > >-python3_5" |
28 |
> > > > > |
29 |
> > > > > The following REQUIRED_USE flag constraints are unsatisfied: |
30 |
> > > > > python? ( exactly-one-of ( python_single_target_python2_7 |
31 |
> > > > > |
32 |
> > > > >python_single_target_python3_4 python_single_target_python3_5 ) ) |
33 |
> > > > > |
34 |
> > > > > ....... |
35 |
> > > > |
36 |
> > > > Start with "grep - ir python /etc/portage". That found the source of |
37 |
> > > > the |
38 |
> > > > problem on one of my systems, I was setting PYTHON_SINGLE_TARGET for |
39 |
> > > > one |
40 |
> > > > package. |
41 |
> > > |
42 |
> > > Thanks Neil, I already had a look just in case I had set something up |
43 |
> > > and |
44 |
> > > forgot about it. This is all it showed: |
45 |
> > > |
46 |
> > > # grep -ir python /etc/portage |
47 |
> > > /etc/portage/package.use/package.use:=media-libs/lcms-1.19-r1 python |
48 |
> > |
49 |
> > How about `emerge --info | grep PYTHON_SINGLE_TARGET'? The problem looks |
50 |
> > |
51 |
> > to be: |
52 |
> > > PYTHON_SINGLE_TARGET="-python2_7 -python3_4 -python3_5" |
53 |
> > |
54 |
> > At least one PYTHON_SINGLE_TARGET needs to be set. I'd guess that |
55 |
> > PYTHON_SINGLE_TARGET got updated to 3.6, leaving GDB in its dust. |
56 |
> > |
57 |
> > Alec |
58 |
> |
59 |
> Thanks Alec, yes python-3.6 was moved to the stable tree. This is what I |
60 |
> have: |
61 |
> |
62 |
> PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" |
63 |
|
64 |
Errm ... no I don't! |
65 |
|
66 |
This morning after an update the targets have moved back to ... python3_5, |
67 |
despite having set up with eselect python3_6. |
68 |
|
69 |
Is the default python target determined by the profile and does this override |
70 |
choices through eselect? |
71 |
|
72 |
Should 'eselect python update' set 3.6 as the default when emerge seems to be |
73 |
determined to use 3.5? |
74 |
|
75 |
|
76 |
# eselect python list |
77 |
Available Python interpreters, in order of preference: |
78 |
[1] python3.6 |
79 |
[2] python3.5 |
80 |
[3] python3.4 (uninstalled) |
81 |
[4] python2.7 (fallback) |
82 |
|
83 |
|
84 |
While from emerge --info I get: |
85 |
|
86 |
PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" |
87 |
|
88 |
|
89 |
I don't fancy rebuilding libreoffice + 67 more packages on 3 PCs just for |
90 |
grins. |
91 |
|
92 |
-- |
93 |
Regards, |
94 |
Mick |