TORTOISESVN Client access frequently asked questions and related causes analysis

reproduced from: http://wolfgangkiefer.blog.163.com/blog/static/8626550320114374759951/ TORTOISESVN Client Access frequently asked questions and related reasons 1. Svn:server sent unexpected return value (Internal Server Error) in response to OPT Ions request for ' http://svn.moon.ossxp.com/svn/test ' Bad user name

Check that the user name of the login is entered incorrectly
SVN: The server sent an unexpected return value (Internal server Error) in response to "OPTIONS" in the request "Http://svn.moon.ossxp.com/svn/test"
2. Svn:options of ' http://svn.moon.ossxp.com/svn/test ': Authorization failed:could not authenticate to server:rejected Basic Challenge (http://svn.moon.ossxp.com)
Bad password
Log in with the correct username/password
SVN: Method options failed with "Http://svn.moon.ossxp.com/svn/test": Authentication failed: Could not authenticate to server:rejected Basic challenge (http://svn.moon.ossxp.com)
3. Svn:server sent unexpected return value (403 Forbidden) in response to OPTIONS request for ' http://svn.moon.ossxp.com/ Svn/test '
User has no permissions
Contact Administrator to assign permissions to users
SVN: The server sent an unexpected return value (403 Forbidden) in response to the "OPTIONS" Request "Http://svn.moon.ossxp.com/svn/test"
4. Svn:options of ' http://www.moon.ossxp.com/svn/test ':-OK (http://www.moon.ossxp.com)
Server address error, normal Web page, SVN WebDAV protocol not supported
Verify that the correct SVN service address is entered. You can enter this address in the browser to confirm
SVN: Method options failed in "Http://www.moon.ossxp.com/svn/test": "OK" (http://www.moon.ossxp.com)
5. The version of your Subversion (client) is below 1.5.0, upgrade to 1.5.0 or above. SVN below 1.5.0 can not handle mergeinfo properly. It can mess up our automated merge tracking!
is because the client software version is lower than the 1.5.0 caused. The server side limits the client software version to avoid damage to merge tracking.
Upgrade local subversion client software to 1.5.0 or later.
6. Svn:this client is too old to work with working copy '. You are need to get a newer Subversion client, or to downgrade this working copy. Http://subversion.tigris.org/faq.html#working-copy-format-change for details.
Multiple versions of the SVN client (tsvn,subclipse,...) are installed, and the versions of each client are inconsistent. The high version of the SVN client automatically updates the file format in the. SVN directory in the local working directory, causing the old SVN client to continue accessing the local working directory
Update all SVN clients installed on this computer to the same large version to avoid inconsistent formatting of the local working directory
SVN: This client is too old for the working copy "." You need to get updated Subversion client, or demote working copy. See Http://subversion.tigris.org/faq.html#working-copy-format-change for more detailed information.
7. svn:working copy ' trunk/src ' locked svn:run ' svn cleanup ' to-remove locks (type ' svn help cleanup ' for details)
An exception operation caused the directory to not unlock.
A simple way to reproduce: Create an empty file named Lock under the. SVN directory
Remove a lock using the command line "SVN cleanup" or a similar "cleanup" action
SVN: Working copy "TRUNK/SRC" has locked svn: Run "svn cleanup" delete lock (enter "SVN help cleanup" for usage)
8. No author information in the log:------------------------------------R9 | (no author information) | ... ossxp.com anonymous commit test
Anonymous commit causes no author information
Check version library permission control, prohibit anonymous submission
9. Sending ... Transfer file data. SVN: Submit failed (details below): Svn:commit blocked by Pre-commit Hook (exit code 1) with output: Submission instructions should contain at least 4 characters, or too simple.
This is because the user submits the submission description (commit log), which is too simple. You need to enter a meaningful commit log at the time of submission.
Write meaningful submission instructions or request an administrator to change the library plug-in
10. Increase logger.c transfer file data. SVN: Submit failed (details below): Svn:commit blocked by Pre-commit Hook (exit code 1) with output:wide character I N Print at/opt/svn/svnroot/myrepos/hooks/scripts/check-case-insensitive.pl line 259. Discovery file name Case conflict: Trunk/src/logger.c already exists in logger.c
The administrator has set up a check for files that have the same name as the new file (only the case is different). File name is different case, checking out on Windows can cause trouble
Do not add duplicate names (different case only) files
Increase src/file aBc.txt transfer file data. SVN: Submit failed (details below): Svn:commit blocked by Pre-commit Hook (exit code 1) with Output:clash: '/trunk/ src/file ABc.txt '/trunk/src/file Abc.txt '
Svn:while preparing '/home/jiangxin/tmp/svn.test/trunk/src/readme.txt ' for commit svn:inconsistent line ending Style
The submitted file has the Svn:eol-style attribute set, but the newline character in the text has a DOS newline character CRLF, as well as a Unix newline character LF, inconsistent.
Unify line breaks within the text file. Linux can use Dos2unix, Unix2dos, sed, and other commands. UltraEdit can be converted under Windows.
SVN: svn: Inconsistent line end style when preparing "/home/jiangxin/tmp/svn.test/trunk/src/readme.txt" for commit operations
svn:failed to add file ' Makefile ': An unversioned file of the same name already exists
Perform update (SVN up) times wrong. There is a file with the same name (not version control) because someone else is adding a file to the server
Rename the local name file first, then perform "svn up", then compare and merge the files. or perform "SVN up--force"
SVN: Adding file ' Makefile ' failed: version-controlled files with the same name already exist
Adding Src/makefile Svn:commit failed (details follow): Svn:file '/svn/test/trunk/src/makefile ' already exists
Add new file, submit the times wrong. Because other people have added the file before me.
Perform the update operation first ("SVN up") and follow the prompts: Merge/submit ...
Add Src/makefile SVN: Commit failed (details below): svn: File "/svn/test/trunk/src/makefile" already exists
$ svn up Conflict discovered in ' Makefile '. Select: (p) postpone, (DF) Diff-full, (e) Edit, (MC) Mine-conflict, (TC) theirs-conflict, (s) Show all Options:p C Makefi Le Updated to revision 5. Summary of Conflicts:text Conflicts:1
When multiple people edit the same file at the same time, they may encounter conflicts. Others first submit to me, then when I submit to update first. Updates may encounter conflicts that cannot be resolved automatically
Using tools for conflict resolution
$ svn up finds conflicts in "Makefile". Select: (P) postpone, (DF) Show all differences, (e) Edit, (MC) My version, (TC) Others ' version, (s) Show all options: P C Makefile Update to version 5. Summary of conflicts: Body Conflict: 1
Svn:commit failed (Details follow): Svn:file ' Makefile ' is out of date svn:file not found:transaction ' 6-d ', path '/trunk/src/makefile '
The submitted file has been deleted by someone else
Perform the update operation ("SVN up"), and then resolve the tree conflict by prompting: Delete the file or continue adding ...
SVN: Submit failed (details below): svn: File "Makefile" is obsolete svn:file not found:transaction ' 6-c ', path '/trunk/src/makefile '
Svn:commit failed (Details follow): Svn:file or directory '/trunk/xxx ' is out of date; Try updating svn:resource out of date; Try Updating
Modifications based on the old version are not allowed
Update ("SVN update") before submitting
SVN: Submit failed (details below): SVN: File or directory "/trunk/xxx" is obsolete; please update svn:resource out of date first; Try Updating
Svn:dav request failed; It's possible that the repository's Pre-revprop-change hook either failed or is non-existent svn:at least one property ch Ange failed;  Repository is unchanged Svn:error setting property ' log ': Repository has not been enabled to accept revision; Ask the administrator to create a pre-revprop-change hook
Actions such as modifying a submit note are high-risk operations because the operation is not versioned and is not a recoverable operation. The default is forbidden.
Contact your administrator to enable this version of the associated hooks, allowing you to modify the version properties. See Administrator Hook Settings
Svn:dav request failed; either the Pre-revprop-change hook for the version library failed or no SVN: at least one property change failed; SVN: Set Property "Log" error: Repository has not been E Nabled to accept revision propchanges; Ask the administrator to create a pre-revprop-change hook
18. Transfer file data. SVN: Submit failed (details below): Svn:commit blocked by Pre-commit Hook (exit code 1) with output: ==================== trunk/s Rc/file.c: Property svn:mime-type or Svn:eol-style not set ==================== administrator has enabled the line break property check. Each newly added file must specify a newline character. If the Svn:mime-type property is a text file, you must set the Svn:eol-style property. For binary files, execute the following command: SVN propset svn:mime-type application/octet-stream path/of/file for text files, you can execute the following command: SVN propset svn: Mime-type text/plain path/of/file svn propset svn:eol-style native Path/of/file to avoid manually setting up files each time you add a file, you can enable automatic property settings ...
An administrator has enabled an extension to check for new file newline characters
Set the correct svn:mime-type and/or Svn:eol-style properties for the new file

Related issues:
1.A: User Login system, enter user name and password, the system prompts the following error: 403 Forbidden, this is why?
Q: First, determine whether the input path is correct;
If the path is correct, ask the user and the configuration administrator to determine whether they have access to the configuration library.
2. A: User Login system, enter user name and password, the system prompts the following error: Authorization failed, this is why?
Q: Please confirm that the user password you entered is correct, and if you forget your password, contact your configuration administrator.
3. A: After modifying the file, click on "SVN Commit", the system prompts: Error commit failed, this is why.
Q: Check with the configuration administrator to see if you have write permission for this configuration library.
4. A: When you log on to the server, you can not log in correctly, and prompted the following error message: Could not resolve hostname, what reason?
Q: This problem is because the domain name in the address cannot be resolved, check that the DNS server address settings for TCP/IP are correct. (The domain name is used in our company's address, the problem should not occur directly using IP)
5. A: User login, enter the correct address, press "enter" key, the system has not reacted for a long time, the last occurrence of "bad Request" error, why?
Also called Svn:server sent unexpected return value (= Bad request) in response to COPY Request for error
Q: The reason is Kaspersky's web anti-virus protection feature and SVN conflict: solution:
In the Set-> service-> network settings-> port setting, remove the monitoring of port 80, or in the settings-〉 Protect-〉 Trust Zone-〉 Add-〉 Browse, browse tortoisesvn installation directory tortoisesvn\bin\ TortoiseProc.exe file can be.
6. A: Why the client is unable to submit, report a "clean up" error.
The Q:subversion client writes the log to the local work copy before submitting the content, prevents other clients from doing the operation again, and if there is an error in the commit process, there will be an open log, which only needs to run the cleanup command. You need to perform a "right key->tortoisesvn->cleanup" in the directory or its parent directory.
7. A: Why do you add a file that no one else can see or have in the version library?
Q: The most likely reason is that you add a file using SVN add (if it is tortoisesvn, "right key->tortoisesvn->add ..."), just stating that a file is intended to be added and not actually added to the version library. To add to the version library you must perform an SVN commit (if it is tortoisesvn may be "right-->svn commit ...").
8. A: Why do I delete files locally, but others still exist.
Q: The most likely reason is that you use SVN delete (if it is tortoisesvn may be "right key->tortoisesvn->delete ...") to delete a file, only to indicate that a file is intended to be deleted, Instead of actually deleting to the version library, the version library to be deleted must perform an SVN commit (if it is tortoisesvn may be "right-->svn commit ...").
9. A:SVN has the ability to back up the current version to a previous historical version.
Q: Yes, click on the JSP or Java file you want, click on the right button, "Show Log", click the version you want to restore, right-click "Undo this Version". Click OK and press submit.
10. A:SVN whether to export all additions to the deleted file (for example, the file name and path required for release)
Q: There are the directory files you need to view, right click, "Show Log", select several versions you want to view in the window, right-click "Copy to cut". Open txt, you can change the file, the author, the release, the information are displayed
11. A:SVN Modify a file, such as before submitting, discard changes, how to operate

Q: There is the directory file you need to view, right click, "svn restore", then revert to the uncommitted before the program.
12. Before submitting a file in A:svn, how do I know if someone has also modified the program during the modification of the file, reducing the potential conflict of submission

Q: Send your changes to the file to the repository, called the commit modification. But make sure your files are up to date before you submit them. You can use the tortoisesvn→ update directly, or you can use the tortoisesvn→ check to see which files have been modified locally or on the server.