On Thu, Feb 2, 2012 at 2:48 PM, Konstantin Kolinko <knst.koli...@gmail.com>wrote:
> 2012/2/2 Sam Johnson <samuel.john...@gmail.com>: > > I recently used svn dump / svndumpfilter to extract a partial path from > one > > repository. The dump was created successfully, and I dropped empty revs > and > > renumbered revs. > > > > I used 'svnadmin load --ignore-uid MyRepo < test.dump' to load the dump > into > > an existing repository. The repo had 19 revisions before I started and > > svnadmin load ran successfully, reporting the addition of 5 revisions. > > > > if I go to an existing working directory for this repo and and run > update, > > it reports "At revision 19", instead of updating to revision 24. Using > the > > TortoiseSVN repository browser on this working directory, I don't see any > > evidence of my loaded changes. However, If I checkout the repository > into a > > new working folder, it correctly reports all 24 revisions, and the > > TortoiseSVN repository browser shows all 24 revisions. > > > > Is this expected behavior? Do I have to tell my users to delete their > > working copies, and re-check-out, if I run svnadmin load? > > > > It should not happen. The "svn up" command should have been updated > that wc to rev.24. There is no need to create a new checkout. > > Maybe that wc was looking at a different repository (e.g. to a backup > copy of the original one)? That would explain the thing. > > What versions of software are you using? > > Best regards, > Konstantin Kolinko > Konstantin, Thank you, I don't know how I overlooked it, but the wc was indeed looking at an old repository, and my successful checkouts were from the newly updated repository. How embarrassing :) Sam
