SVN upgrade working copy

by

You have to upgrade your subversion client to at least 1.7.

With the command line client, you have to manually upgrade your working copy format by issuing the command svn upgrade:

Upgrading the Working Copy

Subversion 1.7 introduces substantial changes to the working copy
format. In previous releases of Subversion, Subversion would
automatically update the working copy to the new format when a write
operation was performed. Subversion 1.7, however, will make this a
manual step. Before using Subversion 1.7 with their working copies,
users will be required to run a new command, svn upgrade to update the
metadata to the new format. This command may take a while, and for
some users, it may be more practical to simply checkout a new working
copy.
— Subversion 1.7 Release Notes

TortoiseSVN will perform the working copy upgrade with the next write operation:

Upgrading the Working Copy

Subversion 1.7 introduces substantial changes to the working copy
format. In previous releases, Subversion would automatically update
the working copy to the new format when a write operation was
performed. Subversion 1.7, however, will make this a manual step.

Before you can use an existing working copy with TortoiseSVN 1.7, you
have to upgrade the format first. If you right-click on an old working
copy, TortoiseSVN only shows you one command in the context menu:
Upgrade working copy.
— TortoiseSVN 1.7 Release notes

More Related Contents:

  1. svn commit error [closed]
  2. How do I migrate an SVN repository with history to a new Git repository?
  3. What do “branch”, “tag” and “trunk” mean in Subversion repositories?
  4. SVN: Is there a way to mark a file as “do not commit”?
  5. What are the pros and cons of the SVN plugins for Eclipse, Subclipse and Subversive? [closed]
  6. Retract accidental checkin
  7. Do I really need version control? [closed]
  8. How does Git solve the merging problem? [closed]
  9. Getting the last revision number in SVN?
  10. Why is branching and merging easier in Mercurial than in Subversion?
  11. How to have ‘git log’ show filenames like ‘svn log -v’
  12. How to checkout a specific Subversion revision from the command line?
  13. How do I ‘svn add’ all unversioned files to SVN?
  14. Common Types of Subversion Hooks
  15. Are subversion externals an antipattern?
  16. SVN Repository Search [closed]
  17. How can I keep the original file [commit] timestamp on Subversion?
  18. Is there a Subversion Checkout Hook or something similar?
  19. Using Git to work with subversion: Ignoring modifications to tracked files
  20. One SVN repository or many?
  21. How to configure a HTTP proxy for svn
  22. How do I export (and then import) a Subversion repository?
  23. How do I get a list of all unversioned files from SVN?
  24. Jenkins CI: How to trigger builds on SVN commit
  25. How can I view all historical changes to a file in SVN
  26. How do you branch and merge with TortoiseSVN? [closed]
  27. Is there a way to recover from an accidental “svn revert”?
  28. SVN Mergeinfo properties on paths other than the working copy root
  29. Moving SVN repositories data with history as subfolders into another repository
  30. Why am I getting tree conflicts in Subversion?

Leave a Comment