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

Re: Repository back up, but working copy re-checkout needed

From: Ronald V. Simmons <Van_at_thesimmonses.net>
Date: 2002-06-17 23:29:56 CEST

It would still be extremely helpful to go ahead and commit the fix. Many of us have repositories and clients which are suffering from the exact same problem. I can build and deploy an svn client (since I don't have modified svn code in my local tree I don't mind the new svn co so much) and that will alleviate the bigger problem for me.

thanks

rvs

----- Original Message -----
From: "Karl Fogel" <kfogel@newton.ch.collab.net>
To: "Subversion Dev list" <dev@subversion.tigris.org>
Cc: "Glenn A. Thompson" <gthompson@cdr.net>
Sent: Monday, June 17, 2002 5:15 PM
Subject: Repository back up, but working copy re-checkout needed

> Okay folks, the repository is back up again, but with a catch:
>
> You'll need to check out working copies from svn.collab.net again, due
> to the versioned-resource url format change. Here is the command
> line, so you won't even have to think:
>
> svn co http://svn.collab.net/repos/svn/trunk -d YOUR_WC_NAME
>
> You're probably saying to yourself "But wait, I thought they
> anticipated this a while back and put compatibility code in the client
> so it would automatically expire old-style cached urls?"
>
> Yes, we did, see revision 1863 for the bulk of that change. But it
> looks like we forgot the case where the client sends an opaque vsn
> rsrc url to provide the *base* for an update -- the base against which
> the server should send svndiff data, that is. So now, when you try to
> update an old working copy, this GET request...
>
> GET /repos/svn/!svn/ver/2248/trunk/subversion/include/svn_wc.h HTTP/1.1
> User-Agent: neon/0.21.1 SVN/0.13.0 (dev build)
> Keep-Alive:
> Connection: TE, Keep-Alive
> TE: trailers
> X-SVN-VR-Base: /repos/svn/$svn/ver/295.14.2.96.1.2/trunk/subversion/\
> include/svn_wc.h
> Host: svn.collab.net
>
> ...results in this server response:
>
> HTTP/1.1 400 Bad Request
> Date: Mon, 17 Jun 2002 20:43:46 GMT
> Server: Apache/2.0.39-dev (Unix) DAV/2 SVN/0.13.0 (dev build)
> Vary: accept-language
> Accept-Ranges: bytes
> Content-Length: 741
> Connection: close
> Content-Type: text/html; charset=ISO-8859-1
> X-Pad: avoid browser bug
>
> ... but unfortunately, the client doesn't have any special code to
> notice that response and simply invalidate the cached vsn-rsrc-url.
> It only has such code for the commit case.
>
> Ooops :-). Sorry, folks.
>
> We could, I suppose, commit a fix for this. But you still wouldn't be
> able to update to get the fix :-), so we'd have to mail it out as a
> patch, which people would apply and then rebuild... Not a very smooth
> upgrade path at all.
>
> So given that the smooth upgrade path is already not an option, the
> easiest thing is probably just for everyone to check out again. Note
> that it's okay to check out using a client that is not bleeding edge:
> the initial vsn rsrc urls come from the server, not the client.
>
> -Karl (& Mike & Ben)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 17 23:39:00 2002

This is an archived mail posted to the Subversion Dev mailing list.