You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Srinivas Rao Marri <sr...@gmail.com> on 2009/09/30 19:12:06 UTC

Subversion - Llocked file could not able to commit the changes

we had an issue in subversion, where locked file could not able to commit changes as per (http://svnbook.red-bean.com/en/1.5/svn.advanced.locking.html).

Below are the steps did: 

1. -bash-3.1$ svn add test.txt 
A         test.txt 

2. -bash-3.1$ svn commit -m "test" 
Adding         test.txt 
Transmitting file data .. 
Committed revision 60994. 

3. -bash-3.1$ svn lock test.txt -m "Testing lock for jira issue svn-535" 
Store password unencrypted (yes/no)? no 
'test.txt' locked by user 'raomarrs'. 

4. -bash-3.1$ svn status test.txt 
     K  test.txt 

5. -bash-3.1$ svn status test.txt 
M    K  test.txt 

6. -bash-3.1$ svn info test.txt 
Path: test.txt 
Name: test.txt 
Repository UUID: bdf33566-2d3b-0410-a816-9e75a007db76 
Revision: 60994 
Node Kind: file 
Schedule: normal 
Last Changed Author: raomarrs 
Last Changed Rev: 60994 
Last Changed Date: 2009-09-29 21:42:11 -0400 (Tue, 29 Sep 2009) 
Text Last Updated: 2009-09-29 21:40:49 -0400 (Tue, 29 Sep 2009) 
Checksum: d41d8cd98f00b204e9800998ecf8427e 
Lock Token: opaquelocktoken:a7bc372d-7dda-41fa-a08d-4152f1b2ed2d 
Lock Owner: raomarrs 
Lock Created: 2009-09-29 21:43:09 -0400 (Tue, 29 Sep 2009) 
Lock Comment (1 line): 
Testing lock for jira issue svn-535 

6. -bash-3.1$ svn commit -m "added test content" test.txt 
svn: Cannot verify lock on path '/entertainment/shadow.comedycentral.com/trunk/configs/test.txt'; no matching lock-token available

Any idea what could be the reason?  

Thanks & regards 
Srini

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402247

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Subversion - Llocked file could not able to commit the changes

Posted by Srinivas Rao Marri <sr...@gmail.com>.
Yes it was solved for me.  All I did is build your apache with -enable- 
pie option.  Without this some special characters will go with lock  
files, and during commit your locks will not match.

Thanks
Srini

On Dec 11, 2009, at 7:06 AM, Mark Blokpoel <bl...@hotmail.com>  
wrote:

> Hi, I seem to have the same symptoms with my svn setup. Have you had  
> any luck solving your problem?
>
> I recently migrated two (large) repositories from one server to  
> another. Now users cannot commit files they have locked. Only by  
> unlocking the files they can commit. The error message we receive is  
> below. I suspect something is preventing subversion to modify the  
> locks even when the committer is the lock's owner. Any help is  
> greatly appreciated, because I'm out of ideas...
>
> Description : An error occurred while contacting the repository.
> Suggestion : The server may be unreachable or the URL may be  
> incorrect.
>
> Description : Commit failed (details follow):
>     Status : 175002
>       File : subversion/libsvn_client/commit.c, 867
>
> Description : CHECKOUT of '/svn/programmers/testrepo/!svn/ver/1/ 
> test.txt': Could not read status line: Secure connection truncated
>     Status : 175002
>       File : subversion/libsvn_ra_neon/util.c, 604

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429762

Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.

RE: Subversion - Llocked file could not able to commit the changes

Posted by Mark Blokpoel <bl...@hotmail.com>.
Hi, I seem to have the same symptoms with my svn setup. Have you had any luck solving your problem?

I recently migrated two (large) repositories from one server to another. Now users cannot commit files they have locked. Only by unlocking the files they can commit. The error message we receive is below. I suspect something is preventing subversion to modify the locks even when the committer is the lock's owner. Any help is greatly appreciated, because I'm out of ideas...

Description : An error occurred while contacting the repository.
 Suggestion : The server may be unreachable or the URL may be incorrect.
 
Description : Commit failed (details follow):
     Status : 175002
       File : subversion/libsvn_client/commit.c, 867

Description : CHECKOUT of '/svn/programmers/testrepo/!svn/ver/1/test.txt': Could not read status line: Secure connection truncated
     Status : 175002
       File : subversion/libsvn_ra_neon/util.c, 604

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429745

Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.