| 1 |
Hi. I see that inn is no longer in the tree and I have a local ebuild |
| 2 |
for inn2.6.3, but it won't work because of the following line |
| 3 |
PYTHON_COMPAT=( python2_7 ) |
| 4 |
|
| 5 |
The error I get is: |
| 6 |
* ERROR: net-nntp/inn-2.6.3::local_ebuilds failed (depend phase): |
| 7 |
* No supported implementation in PYTHON_COMPAT. |
| 8 |
* |
| 9 |
* Call stack: |
| 10 |
* ebuild.sh, line 609: Called source |
| 11 |
* '/usr/local/portage/net-nntp/inn/inn-2.6.3.ebuild' |
| 12 |
* inn-2.6.3.ebuild, line 8: Called inherit |
| 13 |
* 'autotools' 'eutils' 'multilib' |
| 14 |
* 'python-single-r1' 'toolchain-funcs' |
| 15 |
* ebuild.sh, line 314: Called __qa_source |
| 16 |
* '/var/db/repos/gentoo/eclass/python-single-r1.eclass' |
| 17 |
* ebuild.sh, line 112: Called source |
| 18 |
* '/var/db/repos/gentoo/eclass/python-single-r1.eclass' |
| 19 |
* python-single-r1.eclass, line 269: Called |
| 20 |
* _python_single_set_globals |
| 21 |
* python-single-r1.eclass, line 209: Called _python_set_impls |
| 22 |
* python-utils-r1.eclass, line 156: Called die |
| 23 |
* The specific snippet of code: |
| 24 |
* die "No supported implementation in |
| 25 |
* PYTHON_COMPAT." |
| 26 |
|
| 27 |
I still have python 2.7 probably because of issues in building |
| 28 |
chrome, so how do I fix things to keep portage happy and what should I |
| 29 |
do going forward because I obviously don't want to depend on |
| 30 |
python2.7 for actually running things. |
| 31 |
|
| 32 |
I have mailman which I have to do something about as well, so I will |
| 33 |
have to use their new ecosystem or switch to another mailing list |
| 34 |
manager. |
| 35 |
|
| 36 |
Thanks for any advice and thoughts on this subject. |
| 37 |
|
| 38 |
-- |
| 39 |
Your life is like a penny. You're going to lose it. The question is: |
| 40 |
How do |
| 41 |
you spend it? |
| 42 |
|
| 43 |
John Covici wb2una |
| 44 |
covici@××××××××××.com |
Archives