Ryan Schmidt <subversion-2007b@ryandesign.com> writes:
> On May 27, 2007, at 15:27, Kendall Shaw wrote:
>
>> Ryan Schmidt writes:
>>
>>> On May 27, 2007, at 14:06, Kendall Shaw wrote:
>>>
>>>> I have a repository that I created in linux with subversion 1.3.2
>>>> and
>>>> I use a 1.4.3 client on macosx. After checking in changes with the
>>>> 1.4.3 client, when I use svn -u status within my working copy on
>>>> linux, it complains This client is too old to work with working copy
>>>> '.';...
>>>>
>>>> I understand I need to get a more recent client, but I'm curious to
>>>> know how using the 1.4.3 client on my mac to access my
>>>> respository on
>>>> linux (presumably served by the 1.3.2 server), caused my
>>>> working copy on linux to be incompatible with the 1.3.2 client?
>>>
>>> The only way this is possible is if both the Mac and the Linux
>>> machine are in fact using the same working copy, maybe through a
>>> network share of some kind. Usually, each client/computer/user would
>>> have his/her/its own working copy, so that it does not matter if one
>>> upgrades Subversion and the other does not.
>>
>> They are not sharing the working copy, and are on separate machines.
>
> Hmm.....
>
> How is the repository being served? If you're serving with the
> file:/// protocol then all clients will need to be updated, since in
> this setup the client is the server (though I would have expected a
> better error message, one that didn't refer to the working copy but
> to the repository). But if you're serving with another protocol and
> thereby running an actual Subversion server, I don't see how you
> could be getting that message unless you were sharing the working
> copy.
I get at the repository through my apache httpd server.
I suppose it's possible that I accidentally mounted my linux file
system on the mac over samba, and updated the files there... It seems
rather unlikely.
I checked out the files again and it seems to be fixed.
Since I don't know exactly what steps led to the problem, I'll skip over it.
I checked out the files again and it seems to be fixed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 27 23:37:28 2007