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

Re: svn up problem...

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-06-10 16:26:52 CEST

Joerg Hessdoerfer <Joerg.Hessdoerfer@sea-gmbh.com> writes:

> It's NOT easy to reproduce, though. I just tried ra_local in a new
> repository with 2 files, and voila, works as expected. (Read: svn up
> works). In my other (quite large, ~500MB) repo, it doesn't (see
> above).
>
> Any ideas?

Yeah, this is definitely a client bug. Looks like another 'ghudson'
bug.

Here's my repro recipe, using HEAD:

$ echo "bbo" >> newfile
$ svn add newfile
A newfile
$ svn ci -m "add newfile"
Adding newfile
Transmitting file data .
Committed revision 6.
$ svn up
At revision 6.
$ svn up -r 5 newfile
D newfile
Updated to revision 5.
$ more .svn/entries

[... newfile is GONE from entries file, rather than being marked 'deleted' ]

$ svn up
At revision 6.

[... ugh, newfile didn't get re-added, because the client told the server
(erroneously) that it "had a complete rev. 5 of parent directory". ]

Oh wait... this looks like issue #919:

   http://subversion.tigris.org/issues/show_bug.cgi?id=919

Yup. This is a known bug. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 10 16:28:41 2003

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.