17

My tortoise SVN has one issue related with the externals file that I'm unable to identify, this is happening during the checkout process.

After do "commit" and download one fresh checkout this path has this unexpected status.

Exernal Failed: C:\Archive\test4\src\STM\SDK_A18_C052 Error: The specified path has an unexpected status

Please verify my external related to this path:

url: ^/Platform/Integration/ST_40/trunk/src/STM/SDK_A18_C052 local path: src/STM/SDK_A18_C052

1- I tried to create the externals again.

2- I tried to delete this directory and create it again.

3- I tried to realocate this file.

4- I tried to redo the checkout.

Best Regards, Mr. Desperate Man

Victor HD
  • 171
  • 2
  • 5

7 Answers7

19

How I fixed this problem:

  1. Remove external from svn:externals
  2. Make SVN update
  3. Add external back to svn:externals
  4. Make SVN update
Delimitry
  • 2,987
  • 4
  • 30
  • 39
6

I had the same issue with an external file and was unwilling to make a commit (as suggested by Shadow76)

In this bug report I found the following procedure without a commit:

  1. change the local name of the external (file or folder)
  2. make an SVN Update
  3. change the local name of the external back to before step 1
  4. make another SVN Update

which resulted in a successful external.

Community
  • 1
  • 1
hardmooth
  • 1,202
  • 2
  • 19
  • 36
  • 1
    It might have been enough to delete the local (external) file and update from the repository – hardmooth Aug 29 '15 at 07:53
  • Your answer worked, during some years we never had this issue in the past, but now isn't working, probably it was a conflict generated by some reason in the next attempt I'll delete the files at the project and commit again. – Victor HD Sep 22 '15 at 23:25
  • 2
    This worked! To make it clearer: In your working copy open the SVN properties of the folder, edit externals and change the local name of the external in question here. Then do the update. After that you can revert the props and update again. – JCH2k Mar 21 '16 at 14:31
  • @VictorHD: If my answer worked, would you accept my answer? See here: http://meta.stackexchange.com/a/5235/300359 – hardmooth Apr 20 '16 at 07:06
6

Inspired from the post above I have used another step (step 3) where you don't need to create the external again but do revert. After the change the steps look like:

  1. Remove external from svn:externals
  2. Make SVN update
  3. Revert
  4. Make SVN update
Kosta Stojanovski
  • 143
  • 1
  • 9
3
  1. Remove external
  2. Commit
  3. Remove folder for external
  4. Commit
  5. Add external again
  6. SVN Update
Shadow76
  • 61
  • 5
3

I had the same issue recently. It turned out my external conflicted with an existing folder in my repository.

You can use repo-browser to look for a conflicting folder in your repository. If you find a folder that matches the local path of your external, you'll have to delete or rename the offending folder in your repository, or use a different local path for your external.

mcdon
  • 4,931
  • 3
  • 38
  • 36
1

For me there was no need to rename or commit anything.

I found useful information here at stackoverflow
and after reading it, I just tried switch command and kept the path (so I did not actually switch), which caused the faulty external file to be deleted and re-added.

Problem solved in 1 step.

Community
  • 1
  • 1
Tobias Knauss
  • 3,361
  • 1
  • 21
  • 45
1

Easy way to solve this problem without commit or add externals:

  1. Remove external file from svn - properties - externals
  2. Remove external file itself
  3. Run svn update .
  4. Run svn revert . //revert root directory
  5. Run svn update .
Jozhn
  • 11
  • 1