Re: svndumptool and svn:externals

2015-04-21 Thread Ryan Schmidt
On Apr 20, 2015, at 6:56 AM, MOKRANI Rachid wrote: > I moved my SVN server, and now I need to change our svn:externals path. > > I saw that svndumptool can help me to do that, but I don't know exactly the > syntax command to run. > > > My old SVN server is: > http://my_old_server/ > > I can

Merge from a branch of a branch to trunk, losing files

2015-04-21 Thread Robert Voliva
Hello, I created a branch off of trunk. Files were added to that branch. A branch was created off of that branch. Files were added/changed in that branch. The second branch was merged back to trunk. The files added in the first branch, before the second branch was cut from it, were not includ

RE: The XML response contains invalid XML

2015-04-21 Thread OlePinto
I did, but we haven't found anything worthy. The file follows. resetlog.txt The client's machine is running a McAffee, before and after the fix. The server is running some antivirus, which we even switched off to test (no change)

RE: The XML response contains invalid XML

2015-04-21 Thread Bert Huijben
> -Original Message- > From: OlePinto [mailto:olepinto+...@gmail.com] > Sent: dinsdag 21 april 2015 12:20 > To: users@subversion.apache.org > Subject: Re: The XML response contains invalid XML > > We have finally fixed it, although we sadly do not really know what the > problem was. > The

Re: The XML response contains invalid XML

2015-04-21 Thread OlePinto
Hello, I am having the same problem (more or less). We have thoroughly investigated it in-house, but have no more clues about what to look for. I'll begin saying the server is running under Glassfish + SCM, in case it switches a light before going on reading. We can reproduce the problem doing a me

Re: The XML response contains invalid XML

2015-04-21 Thread OlePinto
We have finally fixed it, although we sadly do not really know what the problem was. The magic medicine has been: run /netsh int ip reset c:\filename.log/, reset, reconfigure the network, and done! So it seems it was a client problem, but I don't really know even what kind of problem it was. Did it