Hi,
I think that these question is not for me, but to the development staff.
But as a user, if I got a message like these, certainly that I will look
at my NFS server first, instead the of the SVN.
Att.
Celso Suzuki
Em 21-02-2013 10:46, Stefan Sperling escreveu:
On Thu, Feb 21, 2013 at 09:4
On Thu, Feb 21, 2013 at 09:47:34AM -0300, Celso Tadao Suzuki wrote:
> Hi,
>
> Yes, you are right again.
> I ran the nfslock service and the svn is working fine now.
>
> Thank you for your attencion.
>
Perhaps we should apply a patch like this?
(I haven't run the tests on it yet.)
[[[
* subver
Hi,
Yes, you are right again.
I ran the nfslock service and the svn is working fine now.
Thank you for your attencion.
Best Regards
Celso Suzuki
Em 21-02-2013 09:20, Philip Martin escreveu:
Celso Tadao Suzuki writes:
*The NFS server is a Linux box with Red Hat 5. Kernel **2.6.18-53.1.4.e
Celso Tadao Suzuki writes:
> *The NFS server is a Linux box with Red Hat 5. Kernel **2.6.18-53.1.4.el5PAE**
> **
> **I mount with these options */*exec,dev,suid,rw,noauto*/
> stat64("/home2/celso/SVN/tcf/.svn/tmp/wcng/.svn/wc.db", 0xbfa22a58) = -1
> ENOENT (No such file or directory)
> open("/h
Celso Tadao Suzuki writes:
> My directory is at a NFS FS so I could execute these test.
>
> Well, but even if I don't want to keep my work copy and get a new one on my
> directory the same error occurs
> why if there is no meta data ?
> *[celso@sfw06 tcf]$ cd ..
> [celso@sfw06 SVN]$ svn co
Hi,
I tried as Mr Sperling suggested.
I ran tye cleanup command at a 1.6 client.*
**[celso@sfw11 tcf]$ svn cleanup**
**celso@svn's password: **
**Connection to svn closed.*
After that I tried the upgrade command at 1.7 client.
*[celso@sfw06 tcf]$ svn upgrade**
**svn: E200033: database is locked,
Hi,
Thank you for your aswer.
No, I didn't had.
But no, there were no effect.
*[celso@sfw06 tcf]$ svn cleanup**
**svn: E155036: Please see the 'svn upgrade' command**
**svn: E155036: Working copy '/home2/celso/SVN/tcf' is too old (format
10, created by Subversion 1.6)**
**[celso@sfw06 tcf]$ svn
On Wed, Feb 20, 2013 at 08:51:25PM -0500, Gavin Baumanis wrote:
> Have you tried performing a;
> svn cleanup of your local working copy and then the upgrade?
Yes, this is recommended. Try running 'svn cleanup' with a 1.6
client, and then try running 'svn upgrade' with a 1.7 client.
Keep in mind t
Just while you wait for a more considered response...
Have you tried performing a;
svn cleanup of your local working copy and then the upgrade?
Gavin
From: Celso Tadao Suzuki [mailto:celso.suz...@digitro.com.br]
Sent: Wednesday, 20 February 2013 12:32
To: dev@subversion.apache.org
Subject: P
9 matches
Mail list logo
