Subversion error information list

Here, I will post all the items I have prepared, and I will also download the documents for you to learn together ~

 
Note:

1. Different clients (command line, tortoisesvn, ankhsvn,
Subclipse, etc.) error information may be slightly different.

2. The error information in the following table is in http://svn.moon.ossxp.com/svn/test
The version library is used as an example for reference only.

No.
Error Message
Problem Analysis
Solution

1.
SVN:
Server sent unexpected return value (500 internal server error) in response
Options request for 'http: // svn.moon.ossxp.com/svn/test'
Incorrect user name

Check whether the logon user name is incorrect

SVN: the server sends an unexpected return value (500 internal server error) in the response
In the "options" request "http://svn.moon.ossxp.com/svn/test”

2.
SVN: Options
Of 'HTTP: // svn.moon.ossxp.com/svn/test': authorization failed: cocould not
Authenticate to server: rejected basic challenge (http://svn.moon.ossxp.com)

Incorrect password
Log On with the correct username/password

SVN: method options failed on
"Http://svn.moon.ossxp.com/svn/testfailed: authentication failed: cocould 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
'Http: // svn.moon.ossxp.com/svn/test'
The user has no permissions.
Contact the Administrator to assign permissions to the user.

SVN:
The server sends an unexpected return value (403 Forbidden) in response to the "options" Request
"Http://svn.moon.ossxp.com/svn/test"

4.
SVN: Options
'Http: // www.moon.ossxp.com/svn/test': 200 OK (http://www.moon.ossxp.com)

The server address is incorrect. It is a common web page and does not support the WebDAV protocol of SVN.
Confirm the correct SVN service address. You can enter this address in the browser to confirm

SVN: method options failed at "http://www.moon.ossxp.com/svn/test#: 200 OK"
Http://www.moon.ossxp.com)

5.
The version of your Subversion
(Client) is below 1.5.0, upgrade to 1.5.0 or abve. SVN below 1.5.0 can not
Handle mergeinfo properly. It can mess up our automated merge tracking!

The software version of the client is earlier than 1.5.0. The server imposes restrictions on the client software version to avoid merging and tracking damages.

Upgrade the local subversion client software to version 1.5.0 or later.

6.
SVN: this client is too old
To work with working copy '.'. You need to get a newer subversion client, or
Downgrade this working copy. See
Http://subversion.tigris.org/faq.html#working-copy-format-change for details.

Multiple versions of SVN clients (tsvn, subclipse,...) are installed, and the versions of each client are different. The later version of SVN client automatically updates. Svn in the local working directory.
The file format in the directory. As a result, the svn client of the earlier version cannot continue to access the local working directory.
Update all SVN clients installed on the local machine to the same large version to avoid inconsistent local working directory formats.

SVN: this client is too old for the working copy. You need to obtain the updated subversion client or downgrade the 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'
Remove locks (type 'svn help cleanup' for details)
The directory is not unlocked due to abnormal operations.

A simple reproduction method: Create an empty file named lock under the. SVN directory.
Use the command line "SVN cleanup" or similar "Cleanup" action to delete a lock

SVN: the working copy "trunk/src" has locked SVN: Run "SVN cleanup" to delete the lock (enter "SVN help"
Cleanup "to get usage)

8.
The log does not contain the author information: -------------------------------- R9
| (No author information) |... Ossxp.com anonymous commit Test
Anonymous Submission causes no author information

Check the version library permission control and prohibit anonymous submission.

9.
Sending... transferring file data. SVN: submission failed (details are as follows): SVN: commit
Blocked by pre-commit hook (exit code 1) with output: The submission description should contain at least four characters, or it is too simple.

This is because the submission description (commit log) submitted by the user is too simple. You must enter a meaningful commit log during submission.

Write meaningful submission instructions, or request the Administrator to change the version library plug-in.

10.
Added logger. C to transfer file data. SVN: submission failed (details are as follows ):
SVN: commit blocked by pre-commit hook (exit code 1) with output: wide character
In print at/opt/SVN/svnroot/myrepos/hooks/scripts/check-case-insensitive.pl
Line 259. File Name case-insensitive: Trunk/src/logger. C already exists in logger. c

The Administrator checks whether the new file has the same name (only case-insensitive. File names are case-insensitive, which may cause trouble when detecting files on Windows.

Do not add duplicate files (case-insensitive only)

Add src/file abc.txt to transfer file data. SVN: submission failed (details are as follows): SVN:
Commit blocked by pre-commit hook (exit code 1) with output: clash:
'/Trunk/src/file abc.txt'

11.
SVN: While
Preparing '/home/jiangxin/tmp/SVN. Test/trunk/src/readme.txt' For commit SVN:
Inconsistent line ending Style
SVN: EOL-style has been set for the submitted file
Attribute, but the line breaks in the text include DOS line breaks (CRLF) and Unix line breaks (LF), which are inconsistent!
Unify the line breaks in the text file. In Linux, dos2unix can be used,
Unix2dos, sed, and other commands. In Windows, ultraedit can be used for conversion.

SVN:
SVN: inconsistent row end style when "/home/jiangxin/tmp/SVN. Test/trunk/src/readme.txt" is prepared for the submit operation

12.
SVN: failed to add file 'makefile': An unversioned file of
Same name already exists
An error is reported when an update is executed (SVN up. Because another person adds a file to the server, but a local file with the same name exists (no Version Control)

First rename the local duplicate name file, then execute "SVN up", and then compare and merge the file. Or run "SVN up -- force"

SVN: add files
'Makefile' failed: files with the same name without version control already exist

13.
Adding src/makefile SVN: commit
Failed (details follow): SVN: File '/SVN/test/trunk/src/makefile 'already exists

When a new file is added, an error is returned. Because other people have added this file before me.
Execute the update operation ("SVN up") first, and then follow the prompts to perform the operation: Merge/submit...

Add src/makefile SVN: submission failed (details are as follows): SVN:
The file "/SVN/test/trunk/src/makefile" already exists.

14.
$ 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 makefile updated
To Revision 5. Summary of conflicts: text conflicts: 1

Conflicts may occur when multiple users edit the same file at the same time. If someone else submits the request before me, it must be updated when I submit the request. Conflicts that cannot be automatically resolved during updates
Use tools to resolve conflicts

$ SVN up found a conflict in "makefile. Select: (p) postponed, (DF) show all differences, (e) edited, (MC) My version,
(TC) version of another person, (s) show all options: p c makefile updated to version 5. Conflict Summary: Body conflict: 1

15.
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 another user.

Execute the update operation ("SVN up") first, and then follow the prompts to solve the tree conflict: delete the file or continue to add...

SVN: submission failed (details are as follows): SVN: File
"Makefile" is outdated SVN: file not found: Transaction '6-C', path
'/Trunk/src/makefile'

16.
SVN: commit failed (details follow): SVN:
File or directory '/trunk/XXX' is out of date; try updating SVN: resource out
Date; try updating
Modification Based on the old version is not allowed
Update ("SVN Update") before submitting

SVN:
Submission failed (details are as follows): SVN: the file or directory "/trunk/XXX" is out of date; update SVN: resource out of date first; try
Updating

17.
SVN: Dav request failed; it's possible that
Repository's pre-revprop-change hook either failed or is non-existent SVN:
Least One Property Change failed; repository is unchanged SVN: Error setting
Property 'log': repository has not been enabled to accept revision propchanges;
Ask the Administrator to create a pre-revprop-change hook

Modification submission instructions and other operations are high-risk operations, because the operation is not version-controlled and cannot be recovered. Disabled by default.

Contact the Administrator to enable the hooks for this version and allow you to modify "version attributes ". See administrator hook settings

SVN: Dav request failed; may be from the version Library
Pre-revprop-change hook execution failed or SVN does not exist: at least one attribute change failed; version library does not change SVN: Setting attribute "log" error:
Repository has not been enabled to accept revision propchanges; Ask
Administrator to create a pre-revprop-change hook

18.
Transfer file data. SVN:
Submission failed (details): SVN: commit blocked by pre-commit hook (exit code 1) with output:
============================== Trunk/src/file. c: attribute SVN: mime-type or SVN: EOL-style is not set
============================= The Administrator has enabled the line break attribute check. A line break must be specified for each newly added file. If the svn: mime-type attribute is a text file
You must set the svn: EOL-style attribute. For binary files, run the following command: SVN propset SVN: mime-type
Application/octet-stream path/of/file for text files, you can run the following command: SVN propset SVN: mime-type
Text/plain path/of/file SVN propset SVN: EOL-style native path/of/File
To avoid manual setting of each added file, you can enable automatic attribute setting...
The Administrator enabled the extension for checking the new file line breaks
Set the correct SVN: mime-type for the newly added file
And/or SVN: EOL-style attributes

From: http://blog.csdn.net/liuhuiyang119/archive/2010/10/08/5927017.aspx