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

Re: svn update --depth=empty WC corruption issue

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Tue, 03 Jun 2008 10:19:55 -0400

"Bert Huijben (TCG)" <b.huijben_at_competence.biz> writes:
> Using current 1.5.x (@31482) and a public collabnet subversion server
> on 1.4.3:
>
> # svn co http://ankhsvn.open.collab.net/svn/ankhsvn/trunk/src/Ankh/Commands/
> commands
>
> ? <snip>.. (username guest, password empty) ?
>
> A commands\AddItemCommand.cs
>
> ?
>
> Checked out revision 4217.
>
> # cd commands
>
> # svn up -r 3900 --depth=empty AddItemCommand.cs
>
> At revision 3900.
>
> # svn up
>
> svn: Checksum mismatch for 'AddItemCommand.cs'; expected:
> '111f5de9b72e194b711b8
>
> 973ff8f37b1', actual: '29536039df6a7786a01c3d161693e44b'

Yes, this is an expected bug (because you used --depth=empty on a file).
We've already fixed this in r31516; the fix may not be in 1.5.0, but it
will be in 1.5.1 and future releases.

That is, it's still incorrect to use --depth=empty on a file, but after
r31516, doing so will no longer have an effect on your working copy, and
you won't get lossage like the above.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-03 16:20:17 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.