Hello,
I'm having a weird issue with subversion: Every command is interrupt with
this:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/home/jabiason/{work}' is too old
(format 10) to work with client version '1.8.10 (r1615264)' (expects format
31). You need
I suggest you do a new, clean checkout. You can just copy the dirty files into
the new working copy.
From: Julio Andre Biason [mailto:jabia...@ucs.br]
Sent: Tuesday, October 21, 2014 12:11 PM
To: users@subversion.apache.org
Subject: svn upgrade does nothing
Hello,
I'm having a weird issue
On Tue, Oct 21, 2014 at 02:10:39PM -0200, Julio Andre Biason wrote:
Hello,
I'm having a weird issue with subversion: Every command is interrupt with
this:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/home/jabiason/{work}' is too old
(format 10)
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
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
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
On Tue, Oct 21, 2014 at 05:03:07PM -0200, Julio Andre Biason wrote:
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
