Without further ado

SVN Checkout checks out the project

Common problems when checking out projects

  • Error message: SVN: Server sent Unexpected return value (403Forbidden) in response to OPTIONS request for’ XXXSVN domain name ‘,
  • User authentication fails: couldnot authenticate to server: Rejected Basic Challenge solution: Re-check your user name and password.
  • SVN: OPTIONS of ‘XXX ‘:200 OK (XXX)
  • Unlock your SVN: SVN: run ‘SVNcleanup’ to remove locks Locks your SVN

SVN Commit Commits the project

Frequently asked questions when submitting projects

  • The version of your Subversion (client) is below
  • The SVN version is too old or too high: This client is too old to work with working copy
  • Detection is set, anonymous submission is prohibited… ossxp.com anonymous commit test
  • The file description is too simple: SVN: Commit blocked by pre-commit hook (exitcode 1) with output: The file description to be detected during submission, for example, a five-word or six-word description.
  • 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
  • SVN: While preparing’ file name ‘for commit SVN: Inconsistentline ending style
  • The file already exists: Updates the SVN to find the difference and merges the file to submit the file.
  • The File was deleted: File not found or lost
  • Any style prompt is related to the file format effect, follow up the configuration of the effect rule change file.
  • Another problem is that the file cannot be submitted, which is caused by a file version conflict. In many cases, this problem occurs after SVN migration. At this time, save a local file and delete the special file.
  • Remember to update before submission, update before modification, lest submission overwrite others, or conflict with others, causing unnecessary trouble.
  • Version behind: No Respond will be submitted later

SVN Update Updates the project

Frequently asked questions when updating a project

  • Conflicted is one or more files conflicted solution that generates three conflicted files, compares files, merges content, submits code, and deletes generated files. Or if you drop your own, update line, change your changes to a file, submit them, and make a backup before you revert. If a conflict occurs during commit, the file will also be generated
  • No code updates: There may be a problem with the software, or it may not have been submitted at all, or SVN may have been migrated, and the version does not match and cannot be updated. Make sure it is not the above two problems, if it is the third problem, then find a random question to submit, if successful, it can be updated.

SVN info Indicates the information about the SVN

  • Run the command line in the current SVN project directory to display a series of related information about the current SVN URL. You can accurately determine whether your SVN address is correct, and verify that the resource file exists and can be synchronized. Save the kind of your SVN submission is wrong, now you can tell him yes!

Svn Relocate resets the Svn address

  • Why use this command? Instead of using Checkout directly? Because this command can keep your local project still, you do not need to download some dependencies or pull the project again, if the project is large, depending on many images, you can imagine how much time is wasted.

Svn log Compares the log function and files

  • I’m not going to write down how to do this but I’ll fill it in later, if necessary. This is a function of showing file differences and comparing files.

  • This is all for today. If you have any questions about specific operations or SVN errors, you can write them in the comments section, and I will answer them with you.