On Thu, Oct 20, 2011 at 01:30:34PM -0500, Les Mikesell wrote: > On Thu, Oct 20, 2011 at 1:07 PM, Stefan Sperling <s...@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?
The unlucky user should simply get a new working copy. Working copies are and have always been considered disposable.
