Re: svn 1.5 commit fails

[Jurko Gospodnetić <ju...@docte.hr>]

  Hi Stefan.

> Hi,
> 
> a simple
> 
> $ svn ci folder1 folder2 -m ""
> 
> crashes if the working copy is in the root drive.
> 
> To reproduce:
> $ SUBST g: d:\development\myworkingcopy
> $ cd g:
> $ svn ci folder1 folder2 -m ""
> This application has requested the Runtime to terminate it in an unusual 
> way. Please contact the application's support team for more information.
> 
> The reason for this is in subversion\libsvn_client\commit.c, line 1555
> 
> Did I mention before that I really hate abort() calls? Instead of 
> getting a usable crashdump which could have given me enough information 
> to get a reproduction recipe, I got nothing. After several mails spread 
> over several days I was finally able to get a reproduction recipe from a 
> user who had this problem.

   I could not reproduce this same behaviour as I do not have command 
line svn available here on Windows but I keep encountering a similar 
issue on Windows XP SP2 with TortoiseSVN 1.5.1 & 1.5.2. (Subversion 
client library 1.5.1).

   It happens on some commits (not sure which but it happens only on 
commits with many files involved) and then that commit can not go 
through unless I manage to remove the correct file(s) from the list of 
files to commit or I commit from the original non-substed folder.

   Just chiming in to get this issue dealt with... :-)

   Best regards,
     Jurko Gospodnetić


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn 1.5 commit fails

[Jurko Gospodnetić <ju...@docte.hr>]

  Hi.

>> a simple
>>
>> $ svn ci folder1 folder2 -m ""
>>
>> crashes if the working copy is in the root drive.
>>
>> To reproduce:
>> $ SUBST g: d:\development\myworkingcopy
>> $ cd g:
>> $ svn ci folder1 folder2 -m ""
>> This application has requested the Runtime to terminate it in an 
>> unusual way. Please contact the application's support team for more 
>> information.
>>
>> The reason for this is in subversion\libsvn_client\commit.c, line 1555
>>
>> Did I mention before that I really hate abort() calls? Instead of 
>> getting a usable crashdump which could have given me enough 
>> information to get a reproduction recipe, I got nothing. After several 
>> mails spread over several days I was finally able to get a 
>> reproduction recipe from a user who had this problem.
> 
>   I could not reproduce this same behaviour as I do not have command 
> line svn available here on Windows but I keep encountering a similar 
> issue on Windows XP SP2 with TortoiseSVN 1.5.1 & 1.5.2. (Subversion 
> client library 1.5.1).
> 
>   It happens on some commits (not sure which but it happens only on 
> commits with many files involved) and then that commit can not go 
> through unless I manage to remove the correct file(s) from the list of 
> files to commit or I commit from the original non-substed folder.

   Ok, I reproduced this using TortoiseSVN 1.5.2. You just need to have 
a repository with two folders and in each of those folders you need to 
have a file. And after you update your sandbox, just modify both files 
and attempt to commit from the root folder.

   Using Windows XP SP3 and this is my exact version information 
collected from the TortoiseSVN about box:

> TortoiseSVN 1.5.2, Build 13595 - 32 Bit , 2008/07/31 17:04:57
> Subversion 1.5.1, 
> apr 1.2.12
> apr-utils 1.2.12
> berkeley db 4.4.20
> neon 0.28.2
> OpenSSL 0.9.8g 19 Oct 2007
> zlib 1.2.3


   This is the folder structure and files on which I can reproduce this 
behaviour every time:

   /
   |--BuildSystem/
   |    |--visualStudioBuild.cmd
   |    |--[...plus some extra files...]
   |
   |--Documentation/
   |    |--user_guide.txt
   |    |--[...plus some extra files...]
   |
   |--[...plus some extra folders here...]


   Using TortoiseSVN I just click on the root folder, choose commit, 
select the two modified files, enter the commit message, press ok and 
presto... 'your application has performed an illegal operation' + 
<send>/<don't send> buttons...

   Hope this helps.

   Best regards,
     Jurko Gospodnetić


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org