On Thu, Oct 20, 2011 at 1:07 PM, Stefan Sperling <stsp_at_elego.de> wrote:
>
>> > I don't understand the question. As a rule, when upgrade fails the
>> > working copy remains usable by the older version of svn.
>>
>> Which you won't have any longer if you or your system administrator
>> has updated the programs.
>
> Well, this is quite an obvious and known issue. The release notes clearly
> say that newer clients do not work with older working copies.
Perhaps it is obvious and known to you. I think the number of error
reports on the list indicates that the scenarios that cause errors are
not generally well understood. And, I'd guess that the current
updaters are mostly self-sufficient developers working on personal
machines and we'll see worse when the packaged updates for popular
multiuser systems start rolling out. That is, OS system updates done
mostly-automatically by an administrator will replace the binaries
without an easy way back, and some users' working copies will upgrade
successfully and some won't. In that scenario, should the unlucky
user try to install his own copy of the old binaries if he can find
them?
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2011-10-20 20:31:06 CEST