SVN common error

Source: Internet
Author: User
Tags subversion client svn

Question 1:'. ' is not a working copy. Can ' t open file '. Svn/entries ':The system could not find the specified path.

Answer: The reason is that the access path entered is incorrect, such as Svn://192.168.6.200/if the last write less "/", this error message will appear.


Question 2:after checkout the file, there is no SVN icon, what is going on.

Answer: Sometimes when the client checkout the file, the SVN system icon will not appear, you can perform a "clean up", you will see the SVN system icon.


Question 3:Why do you add a file that no one else can see or have in the version library?

Answer: The most likely reason is that you just executed "add" without "commit", so that only the local note that a file is intended to be added, but not actually added to the version library, to add to the version library must perform a "commit." The same is true for deleting files.


Question 4:"Commit failed. ...... You are have to update your working copy theThe commit failed and the update operation needs to be performed first.

Answer: Multiple people at the same time modify the same file, before committing others have been preempted to the SVN server, causing the error; Workaround: Update the files in the working copy.


Question 5:prompt file conflict on update: "One or more files are not a conflicted state." ”

Answer: Multiple people at the same time modify the same part of the same file, SVN can not automatically merge, can cause this error; Workaround: Compare the files in the working copy to the server files and manually merge them.


Question 6:"Commit failed;file already exists" commit failed and file * * already exists.

Answer: The version management system is very careful when changing the working copy on your computer. Before doing anything, it is possible to write your intentions to the log files on your computer. However, if an accidental operation is interrupted (for example, your computer crashes when a power outage suddenly happens), the log file record may be inconsistent with your final working state. A suggested solution: first copy the items to be submitted to the other directory, and then update the local file, and then put the copied files back to submit.


Question 7:Working Copy ' * * * locked. Please execute the ' clean up ' command.

Solution: The Subversion client will write a local copy of the work before submitting the log, to prevent other clients to do the operation, if there is an error in the commit process, there will be an open log, to solve this problem needs to perform "cleanup" operations, sorting your computer copy of the work, Clean up the wrong logging so that you can continue the operation.


Question 8:error ' Subversion reported an error while doing a cleanup! ' on clean up execution ' * * ' is not a working copy directory '

Answer: In this case, delete the hidden folder first. The temp file under TMP in SVN, and then execute clean up.


Question 9:because the warehouse and the directory are many, uses TSVN each time selects the directory URL of repository to have many addresses, how to clearit. Like clearing the history of the browser, in what way.

Answer: Right key->tortoisesvn->settings->saved Data, you can clear the things you want, including URL, log, window size, password caching and so on.


Question 10:Some versions show only version numbers and (no date), no more information when you select a table of contents in SVN, and what causes it.

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

Question one:attempted to lock a already-locked dir isn't 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:svn:warning: ' xxxxx ' is already under version control solution?

Add only the appropriate directories to SVN, but do not add files under the directory:
#svn St Uploads|grep ^?| awk "{print/$2}" |xargs svn add-n
Cause: most likely. SVN hidden catalog version information has been modified
Solution:
Delete the. SVN directory in the uploads directory and the following file (keep uploads directory. SVN)
#find uploads |grep ' uploads/[^/.] */.svn ' |xargs RM-RF

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.