Hello,
By "
updating the repository" I assume you mean that you actually updated the working copy (or you have upgraded the repository on the server side, but in this case the repository would have nothing to do).
Note that the "update" operation only fetches changes from the repository into your working copy - the changes committed in the repository since you performed the last update. Any local changes are preserved until you either commit them to the repository, or you revert them.
To be sure there is no "garbage" internal data in your working copy, please do the following:
- Do a cleanup of the whole working copy by using the Clean up action on the root directory of the working copy. The action is located in the contextual menu.
- Do a full update of the working copy by using the Update to revision/depth action on the root directory of the working copy. The action is located in the contextual menu, but only if you are in the All Files mode of the Working Copy view. In the presented dialog box, select HEAD revision and Recursive (infinity) as depth.
Since you mention TortoiseSVN, I assume you are a Windows user. I mention this because there is an option that influences the way how external items are presented in the working copy, but this apply only for Mac OS users.
PS: I've just thought to this - maybe by "
updating the repository" you wanted to say that you committed changes in the repository on some external items and after this they still show as modified. In this case, I can see two possibilities:
- There could be something wrong with the external definitions. Please compare the URLs that define the location of the externals (the values from the "svn:externals" property) and the URL of the externals themselves (use the File Information action to see the real URL of the external item). Those URLs should match.
- There could have been an error in the commit process, making the items being committed in the repository, but not updated accordingly in the working copy. In this case, I think that a simple update should fix the issue. Do a Synchronize before and, if the items are presented as conflicting, just make sure there are the same changes and, if so, revert local ones and update with the repository ones.
In case nothing helps, look in the repository if the commit was performed by using the
History action. If the items were committed, then erase them from your working copy (using a file explorer/manager tool, not the SVN client) and update the parent directory (the one that defines the externals) after. This should fetch them again from the repository.
Let us know how things work.
Best Regards,
Florin