Greetings all.
I am running a Subversion v1.1.4 server with several repositories
behind Apache 2. We have noticed that with a Subversion client v1.2.0,
"svn st -u" works fine. But if you upgrade the client to v1.2.1, you
get the following message (domain obfuscated):
-----
[11:46] queeg:~/svn/ompi/orte/mca % svn st -u
svn: REPORT request failed on
'https://svn.example.com/svn/ompi/trunk/orte/mca'
svn: REPORT of 'https://svn.example.com/svn/ompi/trunk/orte/mca': 501
Method Not Implemented (https://svn.example.com)
[11:46] queeg:~/svn/ompi/orte/mca % svn --version
svn, version 1.2.1 (r15230)
compiled Aug 12 2005, 11:08:40
(snipped)
-----
As proof of it working with the 1.2.0 client:
-----
[11:48] queeg:~/svn/ompi/orte/mca % svn st -u
Status against revision: 6826
[11:48] queeg:~/svn/ompi/orte/mca % svn --version
svn, version 1.2.0 (r14790)
compiled May 27 2005, 09:32:22
(snipped)
-----
Clearly, we should probably upgrade our server to be more recent (but
we're slow to upgrade it, since it's a production server). But if I'm
reading the SVN compatibility policy right, this is supposed to work,
right?
From http://subversion.tigris.org/hacking.html#release-numbering:
-----
2. Upgrading to a new minor release in the same major line may cause
new APIs to appear, but not remove any APIs. Any code written to the
old minor number will work with any later minor number in that line.
However, downgrading afterwards may not work, if new code has been
written that takes advantage of the new APIs.
-----
Did something break in the 1.2.1 client with respect to 1.1.4 servers?
--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 12 17:54:36 2005