| CVS will not list modules - Fedora core 6 [message #190490] |
Mon, 29 January 2007 00:07  |
Eclipse User |
|
|
|
Originally posted by: iburry.aol.com
Greetings,
I am having an issue connecting/listing modules under Fedora core 6. The
set up I'm using is identical to the working setup I use with Eclipse
running on Windows. I connect to the repository using ssh and a key,
rather than a password. The repository information is correct, the key
is available, but when I attempt to list modules, nothing happens. No
errors, no list. If I try checking out by specifying a module name, I
get: "An internal error has occurred during checking out XYZ from CVS."
That is the only feedback I'm getting. There appears to be a similar
issue with Fedora core 4, and the suggested solution is to add:
-Djava.net.preferIPv4Stack=true
to -vmargs. I tried this in the ini file and from the command line, with
no success.
Any help with this issue will be appreciated.
Thanks
-Ian
|
|
|
| Re: CVS will not list modules - Fedora core 6 [message #190500 is a reply to message #190490] |
Mon, 29 January 2007 02:59  |
| Eclipse User |
|
|
|
Originally posted by: wayne.beaton._NOSPAM_eclipse.org
Ian wrote:
> Greetings,
>
> I am having an issue connecting/listing modules under Fedora core 6. The
> set up I'm using is identical to the working setup I use with Eclipse
> running on Windows. I connect to the repository using ssh and a key,
> rather than a password. The repository information is correct, the key
> is available, but when I attempt to list modules, nothing happens. No
> errors, no list. If I try checking out by specifying a module name, I
> get: "An internal error has occurred during checking out XYZ from CVS."
> That is the only feedback I'm getting. There appears to be a similar
> issue with Fedora core 4, and the suggested solution is to add:
>
> -Djava.net.preferIPv4Stack=true
>
> to -vmargs. I tried this in the ini file and from the command line, with
> no success.
>
> Any help with this issue will be appreciated.
> Thanks
> -Ian
That fix did indeed work for me on Fedora 4. I haven't tried 6 yet, so I
can't say with any authority whether or not it should work. Another
thing that worked for me on Fedora 4 was to download a more recent JVM.
The problem disappeared for me when I downloaded the Sun Java 1.5 JRE.
If you don't get any better feedback (there are others on the list who
may have more experience than I with Fedora), try posting this question
on the eclipse.platform newsgroup.
HTH,
Wayne
|
|
|
| Re: CVS will not list modules - Fedora core 6 [message #190508 is a reply to message #190500] |
Mon, 29 January 2007 07:20 |
| Eclipse User |
|
|
|
Originally posted by: iburry.aol.com
Wayne Beaton wrote:
> Ian wrote:
>> Greetings,
>>
>> I am having an issue connecting/listing modules under Fedora core 6.
>> The set up I'm using is identical to the working setup I use with
>> Eclipse running on Windows. I connect to the repository using ssh and
>> a key, rather than a password. The repository information is correct,
>> the key is available, but when I attempt to list modules, nothing
>> happens. No errors, no list. If I try checking out by specifying a
>> module name, I get: "An internal error has occurred during checking
>> out XYZ from CVS." That is the only feedback I'm getting. There
>> appears to be a similar issue with Fedora core 4, and the suggested
>> solution is to add:
>>
>> -Djava.net.preferIPv4Stack=true
>>
>> to -vmargs. I tried this in the ini file and from the command line,
>> with no success.
>>
>> Any help with this issue will be appreciated.
>> Thanks
>> -Ian
>
> That fix did indeed work for me on Fedora 4. I haven't tried 6 yet, so I
> can't say with any authority whether or not it should work. Another
> thing that worked for me on Fedora 4 was to download a more recent JVM.
> The problem disappeared for me when I downloaded the Sun Java 1.5 JRE.
>
> If you don't get any better feedback (there are others on the list who
> may have more experience than I with Fedora), try posting this question
> on the eclipse.platform newsgroup.
>
> HTH,
>
> Wayne
Pointing Eclipse to a more recent version of the JVM did the trick. Thanks
-Ian
|
|
|
Powered by
FUDForum. Page generated in 0.08102 seconds
] 
Search
Help
Register
Login
Home
