From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Java configuration is hosed
Date: Tue, 22 Jul 2008 11:03:00 -0700 [thread overview]
Message-ID: <9acccfe50807221103p4c2a8ddcm210e4b53d91ea21d@mail.gmail.com> (raw)
In-Reply-To: <48861A41.5040401@xs4all.nl>
On Tue, Jul 22, 2008 at 10:34 AM, Dave Jones <Dave.Jones@xs4all.nl> wrote:
> Hi Kevin
>
> Kevin O'Gorman wrote on 22/07/08 18:51:
>>
>> I cannot emerge the latest xulrunner, but the root cause appears to be
>> my Java configuration. I haven't touched it in ages, so I have no
>> idea how this happened.
>>
>> The evidence:
>> treat ~ # eselect java-vm list
>> Available Java Virtual Machines:
>> [1] sun-jdk-1.4
>> [2] sun-jdk-1.6 system-vm
>> treat ~ #
>>
>> So far so good, but
>> treat ~ # java-config --list-available-vms
>> Traceback (most recent call last):
>> File "/usr/bin/java-config-2", line 8, in <module>
>> from java_config_2 import __version__
>> ImportError: No module named java_config_2
>> treat ~ #
>>
>> Which seems to mean there should be a file /usr/bin/java-config-2, but
>> there is not.
>> Where should it come from?
>
> I had the same problem yesterday, ran python-updater to fix it.
>
> That did an awful lot of re-compiling (including OpenOffice), but it worked
> for me.
Yeah, thanks. I tried running elogviewer to look for things like this
and that was broken too, but at least elogviewer was kind enough to
diagnose its own problem and suggest python-updater to fix it. So
I've been running that for a few hours.
You mail at least gives me some hope that the fix is in...
--
Kevin O'Gorman, PhD
next prev parent reply other threads:[~2008-07-22 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 16:51 [gentoo-user] Java configuration is hosed Kevin O'Gorman
2008-07-22 17:00 ` Dale
2008-07-22 17:34 ` Dave Jones
2008-07-22 18:03 ` Kevin O'Gorman [this message]
2008-07-22 20:31 ` Dave Jones
2008-07-22 20:40 ` Rev. Ferris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9acccfe50807221103p4c2a8ddcm210e4b53d91ea21d@mail.gmail.com \
--to=kogorman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox