commit getting failed when adding file from one folder to another folder in same repo.

20 views
Skip to first unread message

vowner

unread,
May 3, 2018, 9:38:41 AM5/3/18
to TortoiseSVN
commit getting failed when adding file from one folder to another folder in same repo.

But in another repositories, This is working fine.


commit failed.PNG

Niemann, Hartmut

unread,
May 3, 2018, 11:19:25 AM5/3/18
to TortoiseSVN on behalf of vowner

The png shows two possible reasons.

(a) this file has been locked by someone else. The “check for modifications” dialog will show you who.

(But be warned that a lock technically belongs to a working copy AFAIK, not to a user, so if you have

two working copies and lock a file in one, you can not commit in the other one.)

(b) a server-side precommit hook tells you that you are not allowed to commit *here*. Ask your server admin for more information and advice.

 

Neither seems to be a TortoiseSVN tool issue at first glance.

 

Mit freundlichen Grüßen
Dr. Hartmut Niemann

Siemens AG
Mobility Division
Rolling Stock
Standardization, Remote Control, Display
MO RS LM EN CCI SRD
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Mobil: +49 173 5342327
mailto:hartmut...@siemens.com
www.siemens.com/ingenuityforlife

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ce11bf96-984a-4444-bd9c-13a06d72704b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

vowner

unread,
May 4, 2018, 1:23:16 AM5/4/18
to TortoiseSVN
HI Nieman,

Thanks. I will give some more explanation on the issue here

Here the user is not using the working copy of the repo.

user is accessing the folders inside a same repo in 2 individual repo browsers. ( one folder in one repo browser and other is anither one)

And he is initiating a direct copy of a folder in the first rep browser to another repo browsers another folder in the same repo.

there he is giving the commit message and getting the error as given in the screenshot.


Note :-  we have verified the rep permission and user have RW permission on both the folders
             The user can perform same action in another repos without any issues.

So we are confused what will be the root cause here. 


Regards
Vowner


On Thursday, May 3, 2018 at 8:49:25 PM UTC+5:30, H. Niemann wrote:

The png shows two possible reasons.

(a) this file has been locked by someone else. The “check for modifications” dialog will show you who.

(But be warned that a lock technically belongs to a working copy AFAIK, not to a user, so if you have

two working copies and lock a file in one, you can not commit in the other one.)

(b) a server-side precommit hook tells you that you are not allowed to commit *here*. Ask your server admin for more information and advice.

 

Neither seems to be a TortoiseSVN tool issue at first glance.

 

Mit freundlichen Grüßen
Dr. Hartmut Niemann

Siemens AG
Mobility Division
Rolling Stock
Standardization, Remote Control, Display
MO RS LM EN CCI SRD
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Mobil: +49 173 5342327

Stefan

unread,
May 4, 2018, 8:37:00 AM5/4/18
to TortoiseSVN


On Friday, May 4, 2018 at 7:23:16 AM UTC+2, vowner wrote:
HI Nieman,

Thanks. I will give some more explanation on the issue here

Here the user is not using the working copy of the repo.

user is accessing the folders inside a same repo in 2 individual repo browsers. ( one folder in one repo browser and other is anither one)

And he is initiating a direct copy of a folder in the first rep browser to another repo browsers another folder in the same repo.

there he is giving the commit message and getting the error as given in the screenshot.


Note :-  we have verified the rep permission and user have RW permission on both the folders
             The user can perform same action in another repos without any issues.

The error has nothing to do with RW permissions. The error is thrown by a pre-commit hook script on your server.
So check your server hook scripts.

Stefan
Reply all
Reply to author
Forward
0 new messages