Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "how to solve the operation errors such as inconsistent updates between the local svn plug-in and the library version of eclipse". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Update svn project tips:

Org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded

Svn: The working copy at'd:\ Administrator\ Workspaces\ MyEclipse 2017 CI\ huamu-goodemall'

Is too old (format 29) to work with client version '1.9.3 (r1718519)' (expects format 31). You need to upgrade the working copy first.

Org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded

Svn: The working copy at'd:\ Administrator\ Workspaces\ MyEclipse 2017 CI\ huamu-goodemall'

Is too old (format 29) to work with client version '1.9.3 (r1718519)' (expects format 31). You need to upgrade the working copy first.

General meaning: version 29.of the project library, version 31 of your svn plug-in, you need to update the version of the project marked to 1.93

Solution 1: right-click the project

Solution 2: open the svn project local path folder

Upgrade the svn version of the project code

Record errors in various other common uses of svn:

The causes of all kinds of errors in SVN and the ways to deal with them

A complete Collection of the causes and treatment methods of all kinds of error prompts in SVN

1.

Svn: Server sent unexpected return value (500Internal Server Error) in response to OPTIONS request for 'http://svn.moon.ossxp.com/svn/test'

Wrong user name

Check whether the login user name is entered incorrectly

Svn: the server sent an unexpected return value (500Internal Server Error) in response to the request "OPTIONS" in "http://svn.moon.ossxp.com/svn/test""

two。

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)

Wrong password

Log in with the correct username / password

Svn: method OPTIONS failed in "http://svn.moon.ossxp.com/svn/test": authentication failure: 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'

The user does not have permission

Contact the administrator to assign permissions to the user

Svn: the server sent an unexpected return value (403 Forbidden) in the request "http://svn.moon.ossxp.com/svn/test"" in response to "OPTIONS"

4.

Svn: OPTIONS of 'http://www.moon.ossxp.com/svn/test': 200OK (http://www.moon.ossxp.com)

Incorrect server address. It is an ordinary Web page and does not support SVN's WebDAV protocol.

Confirm that you enter the correct SVN service address. You can enter this address in the browser to confirm

Svn: method OPTIONS failed in "http://www.moon.ossxp.com/svn/test": 200OK (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!

This is due to the fact that the software version of the client is below 1.5.0. The server restricts the version of the client software to avoid damage to the merge trace.

Upgrade your local Subversion client software to version 1.5.0 or above.

6.

Svn: This client is too old to work with working copy. You need to get a newer Subversion client, or to downgrade this working copy. See 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 different. High-version SVN clients automatically update the file format in the .svn directory in the local working directory, so that older SVN clients cannot continue to access the local working directory

Update all locally installed SVN clients to the same large version to avoid inconsistent formats of the local working directory

Svn: for the working copy of this client "." It's too old. You need to get an updated Subversion client, or downgrade a 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)

The abnormal operation caused the directory not to be unlocked.

A simple reproduction method: create an empty file named lock in the .svn directory

Use the command line "svn cleanup" or a similar "cleanup" action to remove the lock

Svn: the working copy "trunk/src" has been locked svn: run "svn cleanup" to delete the lock (enter "svn help cleanup" for usage)

8.

There is no author information in the log:-- R9 | (no author information) | … Ossxp.com anonymous commit test

Anonymous submission results in no author information

Check the permission control of the version library and prohibit anonymous submission

9.

Sending... Transfer file data .svn: failed to submit (details are as follows): svn: Commit blocked by pre-commit hook (exit code 1) with output: the submission instructions should contain at least 4 characters, or too simple.

This is due to the commit log submitted by the user, which is too simple. You need to enter a meaningful commit log when submitting.

Write meaningful submission instructions, or ask the administrator to change the version library plug-in

10.

Add Logger.c to transfer file data. SVN: failed to submit (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 conflict found: trunk/src/Logger.c already exists in logger.c

The administrator set up to check whether the new file has the same name (only different case). File names vary only in uppercase and lowercase, and checking out on Windows will cause trouble

Do not add files with duplicate names (only case differences)

Add src/ file aBc.txt transfer file data. SVN: failed to submit (details are as follows): svn: Commit blocked by pre-commit hook (exit code 1) with output: Clash:'/ trunk/src/ file aBc.txt''/ 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

The submitted file has the svn:eol-style attribute set, but the newline characters in the text are DOS's newline character CRLF and Unix newline character LF, inconsistent!

Unifies the newline characters within the text file. Under Linux, you can use dos2unix, unix2dos, sed and other commands. UltraEdit can be used for conversion under Windows.

Svn: when preparing "/ home/jiangxin/tmp/svn.test/trunk/src/README.txt" for a commit operation, svn: inconsistent line end style

twelve。

Svn: Failed to add file' Makefile': an unversioned file of the same name already exists

Perform update (svn up) Times error. Because someone else adds a file to the server, but there is a file with the same name locally (no version control)

First rename the local renamed file, then execute "svn up", and then compare and merge the file. Or execute "svn up-force"

Svn: failed to add file 'Makefile': an unversioned file with the same name already exists

13.

Adding src/Makefile svn: Commit failed (details follow): svn: File'/ svn/test/trunk/src/Makefile' already exists

Add a new document, submit the Times error. Because someone else has added the file before me.

First perform the update operation ("svn up"), and then follow the prompts: merge / submit.

Add src/Makefile svn: failed to submit (details are as follows): svn: 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 people edit the same file at the same time. If someone else submits it before me, it will be updated when I submit it. Updates may encounter conflicts that cannot be resolved automatically

Use tools for conflict resolution

$svn up found a conflict in "Makefile". Select: (P) postpone, (df) show all differences, (e) edit, (mc) my version, (tc) other people's version, (s) show all options: p C Makefile update to version 5. Summary of conflict: text conflict: 1

15.

Svn: Commit failed (details follow): svn: File 'Makefile' is out of date svn: File not found: transaction' 6murdling, path'/ trunk/src/Makefile'

The submitted document has been deleted by others

Perform an update operation ("svn up"), and then follow the prompts to resolve the tree conflict: delete the file or continue to add.

Svn: failed to submit (details are as follows): svn: file "Makefile" is out of date svn: File not found: transaction '6murc, 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 of date; try updating

Modification based on the old version is not allowed

Update ("svn update") before submitting

Svn: failed to submit (details are as follows): svn: file or directory "/ trunk/XXX" is out of date; please update svn: resource out of date; try updating first

17.

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 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

Operations such as modifying the submission description are high-risk operations because they are not versioned and are irrecoverable. It is prohibited by default.

Please contact your administrator to enable the relevant hooks for this version and allow you to modify the version properties. See administrator hook settings

Svn: DAV request failed; either the pre-revprop-change hook execution of the version library failed or svn does not exist: at least one property change failed; the version library did not change svn: setting property "log" error: Repository has not been enabled to accept revision propchanges; ask the administrator to create a pre-revprop-change hook

18.

Transfer file data .svn: failed to submit (details are as follows): svn: Commit blocked by pre-commit hook (exit code 1) with output: = trunk/src/File.c: property svn:mime-type or svn:eol-style is not set = the administrator has enabled newline attribute checking. 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 adding files each time manual settings, you can enable automatic property settings.

The administrator enabled the extension to check for new file newline characters

Set the correct svn:mime-type and / or svn:eol-style properties for the new files

This is the end of the content of "how to solve the problem of operation errors such as inconsistent updates between the eclipse local svn plug-in and the library version". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.