Common SVN errors and Solutions

Question 1: '.' is not a working copy. Can't open file'. SVN \ entries ': the system cannot find the specified path.

Answer: The reason is that the entered access path is incorrect. For example, SVN: // 192.168.6.200/if "/" is not entered at the end, this error message is displayed.

Question 2: After the file is checkout, there is no SVN icon. What is the problem?

A: Sometimes, after the client checkout file, the svn System icon is not displayed. You can run "Clean up" to display the svn System icon.

Question 3: why are the added files invisible to others and not in the version library?

Answer: The most likely reason is that you only executed "add" instead of "commit". In this way, you only indicated that a file is to be added locally, but it is not actually added to the version library. To add it to the version library, you must execute "commit ". The same is true for deleting files.

Question 4: "commit failed ....... You have to update your working copy first "failed to submit. You must first perform the update operation.

A: When multiple users modify the same file at the same time, other users have already submitted the file to the svn server before submission, resulting in this error. Solution: update the file in the work copy.

Question 5: A file conflict is prompted during the update: "one or more files are not a conflicted state ."

A: If multiple users modify the same part of the same file at the same time, SVN cannot merge automatically, which will lead to this error. Solution: Compare the files in the work copy with the files on the server, manually merge.

Problem 6: "Commit failed; file already exists" failed to be submitted. The file ** already exists.

A: The version management system is very careful when changing the working copies on your computer. Before doing anything, it tries its best to write your intention to log files on your computer. However, if the operation is accidentally interrupted (for example, your computer crashes when a sudden power failure occurs), the log file record may be inconsistent with your final working status. One suggested solution: copy the file to be submitted to another directory, update the local file, and then store the copied file back for submission.

Question 7: working copy '**' locked. Please execute the 'clean up' command.

A: Before the Subversion client submits the content, it copies and writes logs locally to prevent other clients from performing operations again. If an error occurs during the submission process, there will be uncleared logs, to solve this problem, you need to perform the "clean" operation, sort the work copies on your computer, and clear the error log records so that you can continue the operation.

Problem 8: When you run clean up, the error "Subversion reported an error while doing a cleanup!" appears !" '**' Is not a working copy directory"

A: In this case, delete the temporary files under TMP in the hidden folder. SVN, and then run clean up.

Question 9: because there are many repositories and directories, how can I clear the directory URL of repository each time tsvn is used? What is the method used to clear the history in the browser?

A: Right-click tortoisesvn-> Settings-> saved data to clear what you want, including URL, log, window size, and password cache.

Question 10: When I select a directory named show log in SVN, some versions only show the version number and (no date), and there is no other information. Why?

A: There is a (no date) revision, which modifies the files in a directory that you do not have the permission to access for others.

Question 11: attempted to lock an already-locked DIR is not under Version Control

I deleted the log file in the. SVN directory (I also deleted the offending file in. SVN/props-Base)
Then did a cleanup... then resumed my update.

Question 12: SVN: Warning: 'xxxxx' is already under version control solution?

Only add the corresponding directory to SVN, but do not add files under the directory:
# SVN st uploads | grep ^? | Awk "{print \ $2}" | xargs SVN add-n
Cause: the directory version information hidden by. SVN may have been modified.
Solution:
Delete the. SVN directory under the uploads directory and the files below (retain the. SVN directory under the uploads directory)
# Find uploads | grep 'uploads/[^ \.] */. SVN '| xargs Rm-RF

 

 

 

Attempted to lock an already-locked DIR is not under Version Control
I deleted the log file in the. SVN directory (I also deleted the offending file in. SVN/props-Base)
Then did a cleanup ..
Then resumed my update.

 

 

Question 1: '.' is not a working copy. Can't open file'. SVN \ entries ': the system cannot find the specified path.

Answer: The reason is that the entered access path is incorrect. For example, SVN: // 192.168.6.200/if "/" is not entered at the end, this error message is displayed.

Question 2: After the file is checkout, there is no SVN icon. What is the problem?

A: Sometimes, after the client checkout file, the svn System icon is not displayed. You can run "Clean up" to display the svn System icon.

Question 3: why are the added files invisible to others and not in the version library?

Answer: The most likely reason is that you only executed "add" instead of "commit". In this way, you only indicated that a file is to be added locally, but it is not actually added to the version library. To add it to the version library, you must execute "commit ". The same is true for deleting files.

Question 4: "commit failed ....... You have to update your working copy first "failed to submit. You must first perform the update operation.

A: When multiple users modify the same file at the same time, other users have already submitted the file to the svn server before submission, resulting in this error. Solution: update the file in the work copy.

Question 5: A file conflict is prompted during the update: "one or more files are not a conflicted state ."

A: If multiple users modify the same part of the same file at the same time, SVN cannot merge automatically, which will lead to this error. Solution: Compare the files in the work copy with the files on the server, manually merge.

Problem 6: "Commit failed; file already exists" failed to be submitted. The file ** already exists.

A: The version management system is very careful when changing the working copies on your computer. Before doing anything, it tries its best to write your intention to log files on your computer. However, if the operation is accidentally interrupted (for example, your computer crashes when a sudden power failure occurs), the log file record may be inconsistent with your final working status. One suggested solution: copy the file to be submitted to another directory, update the local file, and then store the copied file back for submission.

Question 7: working copy '**' locked. Please execute the 'clean up' command.

A: Before the Subversion client submits the content, it copies and writes logs locally to prevent other clients from performing operations again. If an error occurs during the submission process, there will be uncleared logs, to solve this problem, you need to perform the "clean" operation, sort the work copies on your computer, and clear the error log records so that you can continue the operation.

Problem 8: When you run clean up, the error "Subversion reported an error while doing a cleanup!" appears !" '**' Is not a working copy directory"

A: In this case, delete the temporary files under TMP in the hidden folder. SVN, and then run clean up.

Question 9: because there are many repositories and directories, how can I clear the directory URL of repository each time tsvn is used? What is the method used to clear the history in the browser?

A: Right-click tortoisesvn-> Settings-> saved data to clear what you want, including URL, log, window size, and password cache.

Question 10: When I select a directory named show log in SVN, some versions only show the version number and (no date), and there is no other information. Why?

A: There is a (no date) revision, which modifies the files in a directory that you do not have the permission to access for others.

Reprinted from: http://summary.iteye.com/blog/1190384