> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: den 13 april 2004 16:05
>
> On Tue, 2004-04-13 at 07:13, Nicklas Norling wrote:
>
> > Wow! That's great news, I'm seing way to much wierd WC "corruption"
> > occuring after our cvs->svn conversion. Sounds like this
> might solve a
> > few problems.
>
> The bug we're fixing has nothing to do with WC corruption.
> It's about 'svn up' stopping when it doesn't have to. It's
> silly for users to be forced to run 'svn up' N times to get
> the update to finish.
I have a feeling it's not real corruption bugs, but users errors
and tools doing wierd things. I did not know what to
call them so I labeled them "corruption" in quotes, sorry.
> There's only a few known WC "corruption" bugs that we know
> about, and they're all filed right now. Most of them have to
> do with interrupting 'svn switch' prematurely. If you have
> specific bugs to report, please let us know!
I have around 50 developers running 1.0.1 Linux server with
TSVN 1.0.3 as the client. I've been trying to help them out as
they get stuck with a working copy where nothing works. Commits
fails, update failes, revert fails, cleanup fails. On several
occations we have had to remove the WC and check things out again.
Unfortunately I haven't been able to get the developers to remember
what they did, and we have not been able (or had the time to) dig
deeper into the problems. I'm keeping my eyes peeled and I'll report
if I find something reproducable.
On average I'd say we have had 1-2 "corrupt" WC's per day the first week.
Now it seems to be more rare (or ppl know what to do to fix it so I don't
hear of it).
/Nicke
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 13 17:17:21 2004