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

Does 'svnamin load' invalidate existing working directories?

From: Sam Johnson <samuel.johnson_at_gmail.com>
Date: Thu, 2 Feb 2012 10:52:06 -0500

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?

Received on 2012-02-02 16:57:16 CET

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

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