Before modifying a project, it is customary to update the project first. Today, update MyEclipse 10 update SVN and always report “RA layer request failed……” please see the figure below:
Solutions:
1
Right click to select “temp” — “switch” — – select depth as full recursive, wait for the check to complete, OK
Reference: http://liuqing9382.iteye.com/blog/642783
Today, after passing the Cr (code review) code audit of SVN, I want to execute SVN CI – M “XXXXXX (submission comments) issue = 3380305”, but the submission failed, SVN reported a mistake
The contents are as follows:
Prompt: “SVN: commit failed (details follow): SVN: ‘/ xxx/YYY/(file or folder path)’ is scheduled for addition, but is missing”
Reason: files/folders submitted with SVN before are marked as “add” status, waiting to be added to the warehouse. If you delete this file at this time, SVN will still try to submit this file when submitting, even though its status is “missing”
Solution: in the command line, use “SVN reverse/xxx/YYY /”, in the graphical interface, right-click — revert, select the file. This tells SVN to return the file to the previous state of “unversioned”, that is, not to make any changes to the file, and then execute the submit command
Error executing SVN update:
svn:Checksummismatchwhileupdating'D:\workspace\demo\test\.svn\text-base\test.php.svn-base';expected:'e46703b45e810605fd7513943533b00f',actual:'5480a41836d19692a1a85e667d222e82'The file identification code is inconsistent between local and remote. Under the condition of ensuring the consistency between the two, use the following methods to solve the problem:
1. Find the directory where the file is located eg: D:// workspace/demo/test \
2. Show all hidden files and find the. SVN/entries file in the directory
3. Remove the read-only attribute of the file
4. Edit the file to find the file
10630test.phpfile29152011-09-23T02:16:30.000000Ze46703b45e810605fd7513943533b00f2011-09-14T06:42:48.305470Z2915yuchangfeng5. Change ‘e46703b45e810605fd7513943533b00f’ to ‘5480a41836d19692a1a85e667d222e82’
6. Save the file and update it again
The XML response contains invalid XML error occurred when the SVN of several colleagues in the company was updated.
I got a clue from Google, which may be related to the Http request.
I remember that the previous project changed the network request method once, and changed the Http protocol to the svn protocol. In addition, the project directory has some external links
Checked the SVN directory of the colleague who reported the error, some directories are http protocol, some are svn protocol. (The external link and the root directory are different)
Checked the normal SVN directory of the machine, all directories are svn protocol.
Solution: Unify the root directory and all external chain request methods into the svn protocol
Analyzing the reason, it may be that when the request protocol was uniformly changed, some colleagues did not check the inclusion of the external chain when performing the relocate operation, resulting in the request protocol of the external chain still being http
Fixed
SSL handshake failed: SSL error: key usage violation in certificate has been detected appears when downloading the source code of SVN linked with HTTPS on Linux server
The reason for the error is that the certificate used by windows is not recognized by Linux
Add the following registry value to the windows registry: (mine is 64 bit)
for 32-bit system: (run regedit – > Find the following registry key – > Add a value of type DWORD)
[HKEY_LOCAL_MACHINE\SOFTWARE\VisualSVN\VisualSVN Server]
"CreateGnuTLSCompatibleCertificate"=dword:00000001for 64-bit system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VisualSVN\VisualSVN Server]
"CreateGnuTLSCompatibleCertificate"=dword:00000001StartVisualSVN Server Manager.(Open virsualSVN server）
Go toAction | Properties | Certificate.
ClickChange certificate…
Select Create new self-signed cetificate.
Next all.
If you run svn again on Linux, you will be prompted with a warning that the certificate generator is not trusted, just select Accept Permanently.
The MacOS is updated to the new version. When executing SVN related command line operations, the following errors appear:
The subversion command line tools are no longer provided by Xcode.Online search, most of the answers are yes
Solution:
sudo rm -rf /Library/Developer/CommandLineTools
xcode-select --install
found invalid after operation:
Then we see: http://zerocorner.com/index/index/detail/id/54.html
The content described is basically the same. According to the idea, the brew is reloaded and the domestic image library is switched https://blog.csdn.net/wueasy/article/details/105304818 ）
Download homebrew
/bin/zsh -c "$(curl -fsSL)"Rerun the SVN installation
brew install svnAfter the installation is completed, execute the SVN related commands, and the prompt message changes to (the reason should be that other versions of SVN were installed at the beginning)::
Warning: subversion 1.14.0_2 is already installed, it's just not linked
You can use `brew link subversion` to link this version.Therefore, according to the command, the command is executed
brew link subversionNew information is prompted:
Linking /usr/local/Cellar/subversion/1.14.0_2...
Error: Could not symlink include/subversion-1/mod_authz_svn.h
Target /usr/local/include/subversion-1/mod_authz_svn.h
already exists. You may want to remove it:
rm '/usr/local/include/subversion-1/mod_authz_svn.h'
To force the link and overwrite all conflicting files:
brew link --overwrite subversion
To list all files that would be deleted:
brew link --overwrite --dry-run subversionThe general meaning is that there is a related soft chain, either delete the old one, or directly implement the forced coverage, and then try to force the coverage
brew link --overwrite subversionThe information is as follows:
Linking /usr/local/Cellar/subversion/1.14.0_2... 161 symlinks createdExecute the SVN help command again, and finally you can use it normally
usage: svn <subcommand> [options] [args]
Subversion command-line client.
Type 'svn help <subcommand>' for help on a specific subcommand.
Type 'svn --version' to see the program version and RA modules,
'svn --version --verbose' to see dependency versions as well,
'svn --version --quiet' to see just the version number.manual version upgrade:
As the SVN of the above version 1.14 is older, consider upgrading the SVN manually
unable to load default svn client
In Eclipse under Win7, subclipse 1.10.x is installed, subclipse and subversion Client Adapter have been selected. however, when creating a new SVN repository, the error unable to load default svn client appears. in
Help –> Install new Software –> Work with: (svn_1.10.x -http://subclipse.tigris.org/update_1.10.x) 选中subclipse 下的Subversion JavaHL Native Library Adpter OK.