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.
Yes, "{work}" is my current working directory, which includes information
that I'm not comfortable sharing, even if there is no way to access, simply
because I'm working for a client and I'd have to ask him permission to
access.
If that makes you happy, "/home/jabiason/foo/bar/zaz/12312", where "12312"
is the branch name -- yes, it's a number and no, "zaz" is not "branches"
because I checked out only the branch I need to work. Personally, path
shouldn't affect the result of a program: It has direct access to its local
repository/data (/home/jabiason/foo/bar/zaz/12312/.svn) and there is
nothing that the base OS can't handle (otherwise I wouldn't even be able to
access my files).
On 21 October 2014 16:34, Stefan Sperling <stsp_at_elego.de> wrote:
> 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) to work with client version '1.8.10 (r1615264)' (expects
> format
> > 31). You need to upgrade the working copy first.
> >
> > I run svn upgrade (even multiple times) but the problem still happens.
>
> Normally 'svn upgrade' should either print nothing and succeed (allowing
> the 1.8 client to operate on the working copy), or it should complain with
> some error message and fail.
>
> I can't explain the behaviour you seem to be describing (no output but
> not success either).
>
> Can you please show how you invoked the svn upgrade command exactly?
> And show the current working directory where you invoked it?
>
> It seems you edited the error message, "/home/jabiason/{work}" is not
> a usual path. Can you please at least give something that looks like
> what you're seeing? If you insist on changing paths, please change the
> path's components to some nonsense but leave the paths as-is otherwise,
> rather than possibly redacting entire portions of a path.
>
--
Enviado via UCSMail.
Received on 2014-10-21 20:42:26 CEST