| 1 |
Update 1: |
| 2 |
- applied comments from TomWij, |
| 3 |
- changed the wording to reflect that 'emerge @world' may not work, |
| 4 |
- shortened the wiki URI, |
| 5 |
- added contact info in case of more issues. |
| 6 |
|
| 7 |
Title: python-exec package move |
| 8 |
Author: Michał Górny <mgorny@g.o> |
| 9 |
Content-Type: text/plain |
| 10 |
Posted: 2013-11-07 |
| 11 |
Revision: 1 |
| 12 |
News-Item-Format: 1.0 |
| 13 |
Display-If-Installed: dev-python/python-exec |
| 14 |
|
| 15 |
Due to the recent issues which caused dev-python/python-exec:0 to be |
| 16 |
removed prematurely [1], we had to perform an urgent package move. |
| 17 |
Since we could not use the automatic updates support in portage, users |
| 18 |
will notice two python-exec packages and possibly blockers. |
| 19 |
|
| 20 |
Currently, dev-lang/python-exec is the real package that contains |
| 21 |
python-exec and that will be used in the future. dev-python/python-exec |
| 22 |
is a virtual package that is kept for compatibility with dependencies |
| 23 |
in already-installed packages. |
| 24 |
|
| 25 |
In the most favorable scenario, the package will be upgraded correctly |
| 26 |
on your next world update if you use the '--deep' (-D) and '--update' |
| 27 |
(-u) options. If you don't want to perform a complete world update |
| 28 |
or if it fails for you, you may as well manually upgrade |
| 29 |
dev-python/python-exec: |
| 30 |
|
| 31 |
emerge -1 dev-python/python-exec |
| 32 |
|
| 33 |
This will cause portage to update both python-exec packages and resolve |
| 34 |
the blockers properly. |
| 35 |
|
| 36 |
Please note that if you have applied any kind of package-specific |
| 37 |
modifications to dev-python/python-exec (such as applying keywords |
| 38 |
through 'package.accept_keywords'), you will need to copy them to |
| 39 |
dev-lang/python-exec as well. |
| 40 |
|
| 41 |
If you have applied keywords to dev-python/python-exec in order |
| 42 |
to unmask Python 3.3 on a stable system, please consider removing |
| 43 |
the keywords and reading our wiki page that explains how to properly |
| 44 |
unmask USE flags [2]. |
| 45 |
|
| 46 |
We apologize for all the inconveniences. If you have any more issues |
| 47 |
with python-exec, please do not hesitate to contact as at #gentoo-python |
| 48 |
IRC channel (@freenode) or the gentoo-python@l.g.o mailing |
| 49 |
list. |
| 50 |
|
| 51 |
[1]:https://bugs.gentoo.org/show_bug.cgi?id=489440 |
| 52 |
[2]:https://wiki.gentoo.org/wiki/Unmasking_non-stable_Python_implementations |
| 53 |
|
| 54 |
-- |
| 55 |
Best regards, |
| 56 |
Michał Górny |
Archives