I had pretty much the idea that "svn upgrade" and "svn upgrade ." were the same, I was just trying to scratch both options out of the list.
Upgrading the directory itself fixed the problem. This makes me think (I'm saying this just seeing the behaviour, I have no idea how the code works): It seems upgrade didn't go deep into the directory structure because the root (of the local repo) was already in the latest version[1]. Does upgrade try to go recursively into all directories, checking for ".svn" and updating if necessary? [1] Which also makes me wonder how a single directory got behind in the update process... On 21 October 2014 16:53, Stefan Sperling <s...@elego.de> wrote: > On Tue, Oct 21, 2014 at 04:42:14PM -0200, Julio Andre Biason wrote: > > I run "svn upgrade" in two different forms: > > > > 1. First, a simple "svn upgrade". No output at all. "svn update" after > that > > fails: > > > > Updating '.': > > svn: E155036: Please see the 'svn upgrade' command > > svn: E155036: The working copy at > > '/home/jabiason/src/work/nephalem/12514-old/nephalem/media' > > is too old (format 10) to work with client version '1.8.10 (r1615264)' > > (expects format 31). You need to upgrade the working copy first. > > > > 2. Then, dunno why, I tried "svn upgrade ." (see the dot at the end of > the > > command). Again, no output and "svn update" fails again. > > The current directory is the default path if not specified, so both of > these invocations did the same thing (whatever they did instead of what > we'd expect they'd do). > > What happens if you run this? > svn upgrade '/home/jabiason/src/work/nephalem/12514-old/nephalem/media' > > > Personally, path shouldn't affect the result of a program: > > This expectation doesn't hold in the case of 'svn upgrade', unfortunately. > It must be passed the path to the top-level directory of a working copy. > I've spent quite some time in the 'svn upgrade' code in an effort to > fix that but to no avail. In some situations (involving nested working > copies of various formats) svn just can't make a well-informed guess. > > Still, if the path you pass is not a working copy root, I'd expect to > see an error such as: > svn: E155019: Can't upgrade '/tmp/svn-sandbox/trunk/gamma' as it is not a > working copy root, the root is '/tmp/svn-sandbox/trunk' > > I'd like to reproduce your problem locally but so far I haven't succeeded > in doing so. > -- Enviado via UCSMail.
