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


From: <cmpilato_at_collab.net>
Date: 2002-12-19 09:00:26 CET

As was pointed out earlier, due to a client bug, some nasty stuff got
into the Subversion source repository. ***THIS WAS NOT A CASE OF
REPOS CORRUPTION***. That is, the repository succeeded in performing
the task the client asked it to do, and no data was damaged or lost or
anything. However, it was certainly a circumstance which highlights a
client frailty, and it has probably affected every developer with a
relatively up-to-date Subversion working copy.

That said, Ben Collins-Sussman <sussman@collab.net> writes:

> So here's what we need to do from here:
> 1. Make sure everyone is running a post r4023 client, so nobody gets
> bitten by issue 1012, accidentally creating bad props.

You heard the man. Upgrade your working copies to post-4023, and
rebuild your Subversion clients.

> 2. Fix the repository. Gstein used his magick python scripts to scan
> our repository, and only this one file has the bad props. Either
> we remove the bogus props from HEAD, or we do dump/load sorcery
> and attempt to change history.

This has been done. As far the repository is concerned, the
propchanges never happened in that revision (I re-added them

> 3. Tell everyone to 'rm -rf hook-scripts; svn up'. It's not enough
> to simply toss the wcprop cache. There's bogus liveprop data
> sitting in the entry itself (the CR is wrong, for example.)
> Easier to rebuild the whole directory.

This is the important part. ALL DEVELOPERS should do this.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 19 09:05:05 2002

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