E175009 upon merge with Subversion 1.8.1

2013-07-28 Thread Stefan Hett 

Hi,

I'm having the following issue with Subversion 1.8.1:

Upon trying to merge a specific (rather large) revision from trunk into 
a branch I'm getting the following error after a few minutes:

"svn: E175009: Missing update-report close tag"

Environment:
TSVN 1.8.1 (also tried via svn-command: svn merge http://[])

Tortoise SVN shows it's build against Serf 1.3.0.

On the server side we use Visual SVN 2.5.10 (build against Subversion 
1.7.10).


The server is accessed via a VPN connection (effective transferrate is 
roughly 60-70 kb/s). The revision I'm trying to merge contains several 
larger binary files (a few MB in total size).


Searching on the web makes me suspicious that these reports ran into the 
same problem I did:

http://codeplex.codeplex.com/wikipage?title=Using%20TortoiseSVN%20with%20CodePlex
http://wiert.me/2013/07/25/svnsubversion-and-codeplex-for-now-stick-to-svntortoisesvn-1-7-x-or-lower/ 
(second issue)


Is there any workaround for the problem? Any further details I can 
provide you with to trace down the issue?


Regards,
Stefan

Re: Unable to commit certain file name with "popup" into svn

2013-07-28 Thread ChoeJenSing 

  
  
Hi, 
  
  here are the screen shot
  
  
  
  Thank you
  Regards,
  Jen Sing
  
  
  On 7/26/2013 10:53 PM, Andy Levy wrote:


  On Fri, Jul 26, 2013 at 12:28 AM, ChoeJenSing  wrote:

  
Hi,

i have searched through the archives and try google for the answer.
but i not able to found the solution.

I try to commit this gif filename =popupMenuBg.gif
but it failed to commit

the images actually comes from
dojo_0.90\dijit\themes\tundra\images\popupMenuBg.gif

please guide me on the log file directory for troubleshooting

SVN version 1.6.11 (r934486), compiled jun 23 2013

  
  
You need to describe the "failure". What error message(s) do you get?
Subversion itself does no filtering of file *names*. Your repository
administrator may have installed a hook script that prohibits such
names, or there may be a file by the same name with different case
already in the repository at that location.

But without you providing the *actual error message*, all that we can
do here is guess.





  Disclaimer : This E-mail is intended only for the use of the individual or entity named above and may contain information that is confidential. If you are not the intended recipients, please immediately notify us by return email and delete it from your system. Any unauthorised dissemination, distribution or copying of this email is strictly prohibited. Thank You.