[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [Subclipse-users] RE: RE: subclipse issues?

From: Alexander Kitaev <alex_at_tmate.org>
Date: 2006-03-01 16:37:52 CET

Hello Andrew,
 
Answering to your last question: JavaSVN does use its own "User-Agent" HTTP
header, it is "JavaSVN" followed by version number (optionally) and
(http://tmate.org/svn/) URL.

Alexander Kitaev,
TMate Software,
http://tmatesoft.com/
http://tmate.org/

 

  _____

From: Andrew Ferguson [mailto:Andrew.Ferguson@arm.com]
Sent: Wednesday, March 01, 2006 15:47
To: users@subclipse.tigris.org
Subject: [Subclipse-users] RE: RE: subclipse issues?

hi Mark,
 
 thanks for the response
 
> I assume you are talking about our update site at the URL:
http://subclipse.tigris.org/update_1.0.x
 
sorry (user error), this explains it - I was using the URL from the
changelog e.g.
<http://subclipse.tigris.org/svn/subclipse/tags/subclipse/0.9.108>
http://subclipse.tigris.org/svn/subclipse/tags/subclipse/0.9.108 which I now
realize is just a view into the development repository..

>> assertion error and a message about "eol || strtok" (or something
similar), ignoring this causing a second assertion failure this time in java
code
>> about R/name and P/name2 mismatching.
> I do not know what would cause th assertion error as that would be in the
> Subversion code, but the second error sounds like the problem you get when

> doing a checkout on Eclipse 3.2 M5 which was fixed by Subclipse 0.9.107.
 
This still happens with 1.0.8, under Eclipse 3.1 release (Version: 3.1.0
Build id: I20050627-1435). I've attached the error message. However, unlike
1.0.5, ignoring the assertion failure now gets a working checkout :)
 
Could it be that we have some non-standard keywords set on our repository?

>> javaSvn does not seem to recognize our repository, although javaHL does.
It gives a HTTP 402 error and says that a path that does exist can't be
found
> Cannot answer that. Is it SSL? Try getting updated to 0.9.108.
 
I've been told this may be because our subversion server is configured only
to allow connections from clients identifying with particular "user-agent"
strings. We've been unable to find in the server logs the failed requests
however so can't confirm JavaSVN is using a different user-agent string.
I'll take this up with the admin of the server and then JavaSVN, but any
clarifications here would be v. welcome :)
 
thanks,
Andrew

-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose the
contents to any other person, use it for any purpose, or store or copy the
information in any medium. Thank you.
Received on Wed Mar 1 16:38:19 2006

This is an archived mail posted to the Subclipse Users mailing list.