1 |
On Sat, 28 Dec 2013 23:44:49 -0700 |
2 |
Joseph <syscon780@×××××.com> wrote: |
3 |
|
4 |
> I've solved the problem by installing meld-1.6.0 from attic, 1.7.0 |
5 |
> and 1.8.2 don't work. I've tried python2.7 and 3.2 make no |
6 |
> difference. |
7 |
|
8 |
I am wondering if the issue your system is having is related to one |
9 |
of the following: |
10 |
|
11 |
------------------------------------------------------------------------- |
12 |
|
13 |
2012-11-06-PYTHON_TARGETS-deployment |
14 |
Title PYTHON_TARGETS deployment |
15 |
Author Michał Górny <mgorny@g.o> |
16 |
Posted 2012-11-06 |
17 |
Revision 1 |
18 |
|
19 |
Recently, a few new Python eclasses have been deployed. As ebuilds |
20 |
migrate, the way they support multiple Python implementations will |
21 |
change. The previous method built Python modules for Python |
22 |
implementations selected through `eselect python'. The new method uses |
23 |
the PYTHON_TARGETS USE flags to explicitly name the implementations the |
24 |
modules shall be built for. |
25 |
|
26 |
If you are running a modern system with only Python 2.7 & 3.2 installed, |
27 |
then you don't have to do anything. The defaults will simply fit you, |
28 |
and let you keep your system up-to-date when new Python versions are |
29 |
deployed. |
30 |
|
31 |
However, if you'd like to use another set of Python implementations, you |
32 |
will need to set PYTHON_TARGETS in your make.conf file appropriately. |
33 |
This variable names the enabled implementations in the standard way |
34 |
common to all USE_EXPAND variables. |
35 |
|
36 |
For example, a setup enabling all major Python implementations would |
37 |
look like: |
38 |
|
39 |
PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5" |
40 |
|
41 |
The variable should list all Python implementations which are going to |
42 |
be used on the system; missing a particular value there will result |
43 |
in missing Python modules. |
44 |
|
45 |
A complete list of all possible values can be obtained using a command |
46 |
equivalent to the following: |
47 |
|
48 |
emerge -1pv dev-python/python-exec |
49 |
|
50 |
For more details, please see the python-r1 User's Guide [1]. |
51 |
|
52 |
[1] http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml |
53 |
|
54 |
------------------------------------------------------------------------------ |
55 |
2013-11-07-python-exec-package-move |
56 |
Title python-exec package move |
57 |
Author Michał Górny <mgorny@g.o> |
58 |
Posted 2013-11-07 |
59 |
Revision 1 |
60 |
|
61 |
Due to the recent issues which caused dev-python/python-exec:0 to be |
62 |
removed prematurely [1], we had to perform an urgent package move. |
63 |
Since we could not use the automatic updates support in portage, users |
64 |
will notice two python-exec packages and possibly blockers. |
65 |
|
66 |
Currently, dev-lang/python-exec is the real package that contains |
67 |
python-exec and that will be used in the future. dev-python/python-exec |
68 |
is a virtual package that is kept for compatibility with dependencies |
69 |
in already-installed packages. |
70 |
|
71 |
In the most favorable scenario, the package will be upgraded correctly |
72 |
on your next world update if you use the '--deep' (-D) and '--update' |
73 |
(-u) options. If you don't want to perform a complete world update |
74 |
or if it fails for you, you may as well manually upgrade |
75 |
dev-python/python-exec: |
76 |
|
77 |
emerge -1 dev-python/python-exec |
78 |
|
79 |
This will cause portage to update both python-exec packages and resolve |
80 |
the blockers properly. |
81 |
|
82 |
Please note that if you have applied any kind of package-specific |
83 |
modifications to dev-python/python-exec (such as applying keywords |
84 |
through 'package.accept_keywords'), you will need to copy them to |
85 |
dev-lang/python-exec as well. |
86 |
|
87 |
If you have applied keywords to dev-python/python-exec in order |
88 |
to unmask Python 3.3 on a stable system, please consider removing |
89 |
the keywords and reading our wiki page that explains how to properly |
90 |
unmask USE flags [2]. |
91 |
|
92 |
We apologize for all the inconveniences. If you have any more issues |
93 |
with python-exec, please do not hesitate to contact as at #gentoo-python |
94 |
IRC channel (@freenode) or the gentoo-python@l.g.o mailing |
95 |
list. |
96 |
|
97 |
[1]:https://bugs.gentoo.org/show_bug.cgi?id=489440 |
98 |
[2]:https://wiki.gentoo.org/wiki/Unmasking_non-stable_Python_implementations |