Upgrade Subversion on CentOS

These days have been plagued by the merging of SVN's branches, and everyone reflects that merging between branches is too much trouble, and sometimes it's not known which version was last merged. There were ways to prevent errors from occurring on the process:

1. Everyone is only merging their own changes

Sometimes a fix will involve changes to multiple people.

2. Each fix will be merged once, lest revise too much, don't remember clearly

Most of the time a fix has to be modified over and over again, and there may be a new need to fix it.

3. When submitting a merger, it is stated in the note which version is merged.

Although it can be written clearly, it is not easy to find in the log, and sometimes merging is to skip some versions.

Everyone is complaining about the merger process, and there has been a serious problem a few days ago. At the time, because of the rush to release, and then the merger, the developer overwrites the code in the release branch with the latest content from the main branch, and some code that has not yet been tested is released. Fortunately, there was no big problem on that day, then there is a stable version of the online. A very real problem lies ahead: How to track the history of mergers well.

A master recommended git, I am not against the use of git, but now instead of git, will inevitably bring more learning costs. But there seems to be no other way to start trying git. In Git's introduction, one notable feature was the merging of traces, and the most unexpected harvest was: SVN from 1.5 (2008). Once again to despise their own ignorance) the beginning of the support of the merge tracking. Then keep using SVN.

Let's give you an account of the project's use of SVN scenario: Centos,apache2 + Subversion

Looking at the current SVN server version (SVN--version) to the server is 1.4, the first thought is to upgrade:

# Yum Update Subversion

It's still a blessing, and now there are 1.6.11 in the warehouse in the Cent OS.

Then use the TORTOISESVN update in the local working directory to get the error message: Could not open the requested SVN filesystem. View httpd on the server Error.log, found: (20014) Internal error:expected FS format ' 2 '; Found format ' 4 '.

When the server-side program is upgraded, the warehouse also needs to be upgraded:

# Svnadmin Upgrade Myrespository

After the warehouse upgrade, restart httpd, and then use the TORTOISESVN update, and get another error: Can ' t open file '/var/www/svn/myrepository/db/txn-current-lock ': Permission denied. It seems that there is a problem with permissions, but Myrepository permissions are Apache.apache, as if there is no problem. Then enter myrepository, view the subdirectory or file permissions, found that one of the new file format belongs to Root.root. In contrast to the format in other directories, this file is problematic and uses:

# chown Apache.apache Format

Be modified. Then restart the httpd service.

After completing the steps above, both the client and server side are working properly.

At this point, when the merge is complete, the merged version becomes grayed out.