On 24/07/13 00:39, Hua Xiang wrote:
2013/7/23 Gary Martin <[email protected]>
On 23/07/13 13:00, Hua Xiang wrote:
Hi Gary,
Commit failed again.
I have attached the error snapshot and the svn info just below, please
help
me to have a look.
Thanks.
<
https://mail.google.com/mail/**u/0/?ui=2&ik=aaa0d8a81e&view=**
att&th=1400b3a78ff42730&attid=**0.2&disp=safe&realattid=ii_**
1400b3a6213f374d&zw<https://mail.google.com/mail/u/0/?ui=2&ik=aaa0d8a81e&view=att&th=1400b3a78ff42730&attid=0.2&disp=safe&realattid=ii_1400b3a6213f374d&zw>
</mail/u/0/s/?view=att&th=**1400b40e0aed4072&attid=0.1&**
disp=emb&realattid=ii_**1400b40bc0079028&zw&atsh=1>
</mail/u/0/s/?view=att&th=**1400b571f94149d0&attid=0.1&**
disp=emb&realattid=ii_**1400b568dbddf769&zw&atsh=1>
$ svn info
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/home/xiang/bep_0008_time_**
series_reports'
is too old (format 29) to work with client version '1.8.0 (r1490375)'
(expects format 31). You need to upgrade the working copy first.
>$ svn --version
svn, version 1.8.0 (r1490375)
compiled Jun 19 2013, 10:42:54 on i686-pc-cygwin
Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software,
seehttp://subversion.apache.**org/<http://subversion.apache.org/>
The following repository access (RA) modules are available:
* ra_svn : Module for accessing a repository using the svn network
protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
- handles 'http' scheme
- handles 'https' scheme
I can't see the attachment you mentioned so it is probably removed.
Otherwise, that error on the svn info command at least tells us that the
copy of the code in /home/xiang/bep_0008_time_**series_reports was
checked out with an older version of svn than you are attempting to svn
info at this point. Your previous response suggested that tortoisesvn is
using subversion 1.7.10 so that ties together at least.
Still want to know why I could commit to trunk rather than to my branch,
using the same svn version?
If you are happy to continue using the command line (and/or you want to
upgrade your tortoisesvn to 1.8) you could follow the advice of the error
message:
svn upgrade /home/xiang/bep_0008_time_**series_reports
Done.
I would expect the svn info command to work assuming that is successful.
Yes! Thanks!
"$ svn info
Path: .
Working Copy Root Path: /home/xiang/bep_0008_time_series_reports
URL:
http://svn.apache.org/repos/asf/bloodhound/branches/bep_0008_time_series_reports
Relative URL: ^/bloodhound/branches/bep_0008_time_series_reports
Repository Root: http://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1505875
Node Kind: directory
Schedule: normal
Last Changed Author: gjm
Last Changed Rev: 1497836
Last Changed Date: 2013-06-28 17:38:30 +0100 (Fri, 28 Jun 2013)
"
Meanwhile, it is not so clear to me whether you attempted a fresh checkout
of the bep_0008_time_series_reports branch.. perhaps the removed attachment
would have told me that though.
Well, the output from "svn info" seems to confirm that you didn't
attempt a fresh checkout with http:// swapped for https:// as I
suggested (or if you tried then perhaps the client ignored you). I was
under the impression that committers should be using the latter.
Anyway, I think this is meant to be a safe way of swapping without
downloading everything again:
svn relocate http:// https:// /home/xiang/bep_0008_time_series_reports
At that point, are you able to "svn commit" the files from the command
line? Do you need a better guide on the svn commands to get you going
given that you were using a client before or can you work these things out?
Cheers,
Gary
