[Reprinted] SVN FAQs and related causes for your reference

1. SVN: server sent unexpected return value (500 internalserver error) in response to 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 to 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 basicchallenge (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: couldnot 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'

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 the response to the "options" request "http://svn.moon.ossxp.com/svn/test”,

4. SVN: Options of '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 on "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 above. 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 to downgrade this workingcopy. See http://subversion.tigris.org/faq.html#working-copy-format-change Fordetails.

Multiple versions of SVN clients (tsvn, subclipse,...) are installed, and the versions of each client are different. The SVN client of a higher version automatically updates the file format under the. SVN directory in the local working 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 details.

7. SVN: working copy 'trunk/src' locked SVN: Run 'svncleanup' to 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" for usage)

8. No author information in the log: ------------------------------------ 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): SVN: commit blocked by pre-commit hook (exitcode 1) with output:
Submission instructions should include at least 4
Or too easy.

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): SVN: commit blocked by pre-commit hook (exitcode 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)

Added 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: inconsistentline ending Style

The SVN: EOL-style attribute has been set for the submitted file, but the linefeed in the text contains the DOS linefeed CRLF and the Unix linefeed lf, Which is inconsistent!
Unify the line breaks in the text file. In Linux, dos2unix, unix2dos, sed, and other commands can be used. In Windows, ultraedit can be used for conversion.

SVN: When "/home/jiangxin/tmp/SVN. Test/trunk/src/readme.txt" is prepared for the Submission operation, SVN: inconsistent row end Style

12. SVN: failed to add file 'makefile': An unversioned fileof the 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: An error occurred while adding the 'makefile' file: the file with the same name but not version control already exists.

13. Adding src/makefile SVN: commit failed (detailsfollow): 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) others' version, (s) show all options: update p c makefile 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): SVN: the file "makefile" is outdated SVN: file not found: Transaction '6-C', path'/trunk/src/makefile'

16. SVN: commit failed (details follow): SVN: file ordirectory '/trunk/XXX' is out of date; try updating SVN: resource out of 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 therepository's pre-revprop-change hook either failed or is non-existent SVN: atleast one Property Change failed; repository is unchanged SVN: error settingproperty '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: The dav request failed. It may be that the pre-revprop-change hook of the version library fails to be executed or SVN does not exist: at least one attribute change fails; the version library does not change SVN: an error occurred while setting the attribute "log": repository has not been enabled to accept revision propchanges; askthe administrator to create a pre-revprop-change hook

18. Transfer file data. SVN: submission failed (details are as follows): SVN: commit blockedby pre-commit hook (exit code 1)
With output: ============================== trunk/src/file. c: attribute SVN: mime-type or SVN: the EOL-style is not set to ======================= the Administrator has enabled the linefeed 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
For text files, run the following command: SVN propset SVN: mime-type text/plain path/of/file SVN propsetsvn: 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 and/or SVN: EOL-style attributes for the new file.

Related questions:

1. A: When a user logs on to the system and enters the user name and password, the system prompts the following error: 403 forbidden. Why?
Q: First, check whether the input path is correct;
If the path is correct, check whether the user and the configuration administrator have the permission to access the configuration library.

2. A: After you enter the user name and password when logging on to the system, the system prompts the following error: Authorization failed. Why?
Q: Check whether the entered user password is correct. If you forget the password, contact the configuration administrator.

3. A: After modifying the file and clicking "SVN commit", the system prompts "error commit failed". Why?
Q: check with the configuration administrator whether you have the "write" permission on the configuration library.

4. A: When logging on to the server, you cannot log on to the server correctly, and the following error message is displayed: cocould not resolve hostname. Why?
Q: The problem is that the domain name in the IP address cannot be resolved. Check whether the IP address of the TCP/IP DNS server is set correctly. (The domain name is used in our company's address. This problem should not occur if we directly use the IP address)

5. A: When you log on, enter the correct address and press "enter". After the system does not respond for a long time, the error "400 bad request" occurs. Why?
Q: The reason is that Kaspersky's Web anti-virus protection function conflicts with SVN: solution:
In "Settings"-> "service"-> "Network Settings"-> "port settings, disable monitoring of port 80; you can also choose "set"> "protection"> "Trust area"> "add"> "Browse" to view the tortoisesvn \ bin \ tortoiseproc.exe file under the tortoisesvn installation directory.

6. A: Why can't the client submit and report the "clean up" error.
Q: Before the Subversion client submits content, it will copy and write 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, run the cleanup command. You must right-click the directory or its parent directory and choose tortoisesvn> cleanup ".
7. A: Why are the added files invisible to others and not in the version library?
Q: The most likely reason is that you use SVN add (if tortoisesvn is used, it may be "right-click-> tortoisesvn-> Add... ") to add a file, only to indicate locally that a file is to be added, but not to the version library, SVN commit must be executed to add to the version Library (if tortoisesvn is used, it may be "right-click-> SVN commit... ").

8. A: Why can't I see the locally deleted files, but they still exist?
Q: The most likely reason is that you use SVN Delete (if tortoisesvn is used, it may be "right-click-> tortoisesvn-> Delete... ") Deleting an object only indicates that the object is intended to be deleted locally, but does not actually be deleted to the version library, SVN commit must be executed for the version library to be deleted (if tortoisesvn is used, it may be "right-click-> SVN commit... ").

9. A: Does SVN have the ability to roll back the current version to a previous version?
Q: Yes. Click the JSP or Java file you need, right-click the file, and choose "show log", click the version you want to restore, and right-click "restore this version ". click "OK" and then click "Submit.

10. A: Does SVN export all added or deleted files (for example, the file name and path to be modified during release)
Q: Go to the directory file you want to view, right-click and select "display log", select the versions you want to view in the window, and right-click "Copy to cut version ". open the TXT file to display the modified file, submitted by, version times, and information.

11. A: modify a file in SVN. If you do not want to modify the file before submitting the file

Q: Go to the directory file you want to view, right-click it, and "SVN restore" to restore the program before submission.

12. A: before submitting a file in SVN, how can I know if someone has modified the program during the file modification period to reduce the possible conflicts during submission?

Q: Send your modifications to the file to the version library. However, make sure that your file is up-to-date before you submit the file. You can directly use tortoisesvn → update, or use tortoisesvn → check the modifications to see which files have been modified locally or on the server.