You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mark Phippard <ma...@softlanding.com> on 2005/12/16 16:59:58 UTC

Problem in 1.3.0 RC-6

I have encountered a problem in 1.3.0 RC-6.  I will explain the problem 
and let you all decide how serious it is.  I do not think it will pose any 
problems for the command line, but it may very well pose problems for 
bindings and other clients.

The problem is in the svn status -u output via DAV.

I initially suspected the problem was caused by the change in r17589 which 
was backported to 1.3.0 in r17593, because that was a fix for a similar 
problem.  My colleague Paul Burba confirmed the problem in debug of RC-6 
and the command line.  However, he has also rebuilt RC-4 and confirmed 
that it has the same problem.  So whatever the cause of the problem, it 
appears it has existed in 1.3.0 all along.

Anyway, the problem is that the URL that represents the item in the 
repository and is passed back in the status structure is "corrupted". 
Occasionally it has the right value, most often it has an empty string but 
sometimes it has a partial string or even a valid URL of a different item.

This causes problems in Subclipse via the JavaHL bindings.  I did not spot 
this before because we only reference the URL when you want to do a 
compare and I did not test that.   The change in r17589 was fixing a 
problem where the lastChangedRevision was not correct.  That is more 
visible in the UI in Subclipse so I based my testing off that. 

Like I said, I do not think the URL is used by the CLI but it is there in 
the structure so might effect other apps that use it.

Paul Burba is building 1.2.x so that he can see if it had this problem or 
not.  I will let him post what he discovers.

Thanks

Mark









_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Problem in 1.3.0 RC-6

Posted by Mark Phippard <ma...@softlanding.com>.
Mark Phippard <ma...@softlanding.com> wrote on 12/16/2005 11:59:58 AM:

> The problem is in the svn status -u output via DAV.
...

> Anyway, the problem is that the URL that represents the item in the 
> repository and is passed back in the status structure is "corrupted". 
> Occasionally it has the right value, most often it has an empty string 
but 
> sometimes it has a partial string or even a valid URL of a different 
item.

I should have posted a recipe.  I guess I didn't because you have to be in 
debug to see it.

I think you could pretty much just run svn st -u on any "out-of-date" WC 
against the normal SVN repository.  When I tested, I checked out r16000 of 
the JavaHL bindings so that I would have a small subset to deal with.  It 
has a nice mix of changes so it makes a good test.

svn co -r 16000 
http://svn.collab.net/repos/svn/trunk/subversion/bindings/java/javahl
cd javahl
svn st -u

Thanks

Mark





_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org