| Summary: | net-libs/nodejs: No supported Python implementation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John L. Poole <prestopoole> |
| Component: | Current packages | Assignee: | Mike Gilbert <floppym> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bugs, patrick |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
environment |
||
|
Description
John L. Poole
2013-11-29 18:12:25 UTC
Created attachment 364210 [details]
build.log
Created attachment 364212 [details]
environment
Exactly which version of python-2.7 do you have installed?
The ebuild is actually missing ${PYTHON_DEPS} in DEPEND.
Thanks for the bug report. It's actually a duplicate of bug 487570. *** This bug has been marked as a duplicate of bug 487570 *** Answer for Comment #3: [I] dev-lang/python Available versions: (2.6) 2.6.8-r3 (2.7) 2.7.5-r3 ~2.7.5-r4 (3.2) 3.2.5-r3 (3.3) ~3.3.2-r2 ~3.3.3 {-berkdb build doc examples gdbm hardened ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml ELIBC="uclibc"} Installed versions: 2.7.5-r3(2.7)(11:04:17 AM 11/29/2013)(gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml -berkdb -build -doc -examples -hardened -wininst ELIBC="-uclibc") 3.2.5-r3(3.2)(11:02:20 AM 11/29/2013)(gdbm ipv6 ncurses readline ssl threads tk wide-unicode xml -build -doc -examples -hardened -sqlite -wininst ELIBC="-uclibc") Homepage: http://www.python.org/ Description: An interpreted, interactive, object-oriented programming language (In reply to John L. Poole from comment #5) eix output tells me nothing about what you have installed, only about what is present in the portage repository. The eix command tells me that I have installed version 2.7.5-r3(2.7). When you asked what version of of 2.7 I had installed, using eix is what I thought would provide you the answer. If you tell me what command to execute to obtain the information you desire I shall gladly execute it and provide the output here. (In reply to John L. Poole from comment #7) > The eix command tells me that I have installed version 2.7.5-r3(2.7). When > you asked what version of of 2.7 I had installed, using eix is what I > thought would provide you the answer. eix uses the background color to indicate installed versions. That obviously gets lost when you paste it into a textarea in a web browser. > If you tell me what command to execute to obtain the information you desire > I shall gladly execute it and provide the output here. If you had simply said "2.7.5-r3", that would be enough; I don't need to see the entire output of some command. However, "equery list dev-lang/python" does produce more useful output when copy/pasting. If you do indeed have dev-lang/python-2.7.5-r3 installed, I do not think this bug is a duplicate of 487570. Can you run the following and tell me if it outputs 0 or 1? portageq has_version / '>=dev-lang/python-2.7.5-r2:2.7'; echo $? A little more information on where I am going with this: If that command outputs 0, then everything is fine and I have no explanation for why nodejs will not build on your system. We will have do do some more poking. If that command outputs 1, then portage does not think you have a new enough version of python:2.7 installed. I would suggest re-installing (and possibly upgrading) python:2.7. emerge --oneshot dev-lang/python:2.7 Here's the command & output requested:
themis portage # portageq has_version / '>=dev-lang/python-2.7.5-r2:2.7'; echo $?
0
themis portage #
Here's what would emerge if I did so:
themis portage # emerge --oneshot dev-lang/python:2.7 -p
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-lang/python-2.7.5-r3
themis portage #
I then went ahead and tried emerging nodejs just to see if I got the same result, and I did not: nodejs successfully installed:
>>> Installing (1 of 1) net-libs/nodejs-0.10.21
I had been updating some other programs (emerge --update...) while this bug was pending, so my system has changed since the inception of this ticket. I'm guessing there was a dependency that was fixed. I regret we didn't get to the bottom of the cause.
|
