![]() It even gives a hint which level of client compatibility the repository bears. Note: Since 1.9, you can use the svnadmin info subcommand to check a repository's features (on the server). The error message invalid filesystem format option 'addressing logical' corresponds to the new FSFS v7 feature "Logical Adressing".Ībout client-server, the compatibility matrix clearly states there is no issue, as far as the server code version supports the FSFS file system version of accessed repositories. If the repository in question was created by a 1.9 server, it seems it may cause compatibility problems with older clients when accessing through file:// protocol. Subversion 1.9 introduced a new version of their FSFS file system (v7), which is the filesystem used in the repository (not the working copy). Note that TortoiseSVN uses the Subversion APIs to communicate with the server, so for client/server compatibility we only need to consider the Subversion versions.Although the OP solved his problem - by going back to an old version of Subversion (probably 1.6.x as he says it's the default shipped with RHEL6.6) - the error symptom poses a valid question which deserves more research. It does not discriminate between versions of 1.8 client and server. You can also check the Subversion feature compatibility chart for the 1.8 release. (Of course, the semantics may change in the trivial ways appropriate for bugfixes, just not in ways that would force adjustments in calling code It may cause bugfixes to disappear/reappear, but API signatures and semantics remain the same. Upgrading/downgrading between different patch releases in the same MAJOR.MINOR line never breaks code. This versioning scheme is outlined in Subversion's inter-release compatibility guidelines, and your question is addressed: 1.8.0 to 1.8.1) to fix bugs and not to introduce or remove features. ![]() Both the Subversion and TortoiseSVN projects use minor release updates (e.g. There are no feature compatibility concerns when both client and server are the same minor version (e.g. But that's not the kind of answer I am looking for :) I have copy of the executable that I can share with whoever in the team requires it. Or will there be any limitations or loss of functionality if a recommended version of client is NOT used for a specific version of server. When I check compatibility in this case, I meant to ask will the client be able to use all the features provided by server. So, some versions of clients do not work well with some versions of server. Or, is it that there is no relationship between the TortoiseSVN client and SVN server versions at all? In which case too, compatibility matrix would certainly help.Īpparently, there are major changes in SVN server version 1.5 and 1.8. I could not find compatibility matrix for TortoiseSVN client and SVN server versions. Since Tortoise SVN client 1.8.7 is not available, can we use a higher version of the client 1.8.9 for SVN server version 1.8.9. ![]() We realized today that Tortoise SVN client version 1.8.7 is no longer available in. So, we we have been using Tortoise SVN client version 1.8.7.
0 Comments
Leave a Reply. |