RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already?

Hi Bert,

________________________________
From: Bert Huijben [mailto:bert_at_qqmail.nl]
Sent: Wednesday, 25 September 2013 6:43 AM
To: 'JANIKOVIC Jan'; users_at_subversion.apache.org
Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already?

                No,

There is no issue for this specific part of those threads created as nobody was able to produce a reproduction recipe for this problem to the developers yet.
Surely it would be useful to add the issue report anyway, even if there is no easy way to reproduce it. After all, it is a known issue now. We can then work on the reproduction recipe.

All the threads you quoted end with this request... So unless you add a way to reproduce the problem (perhaps with the help of the earlier reporters) to the discussion there is not much we can do for you at this time/
I'm sure I posted the method for me to reproduce it. We were running a 1.2.3 server served by Apache 2.0.54 on Windows Server 2003 SP2. I was then using a 1.8.1 client on Windows 7 Pro 32-bit. I thought I'd posted my recipe here:

http://svn.haxx.se/users/archive-2013-08/0035.shtml

However, this is NOT the full recipe. Instead, look at this post:

http://svn.haxx.se/users/archive-2013-08/0140.shtml

That contains the steps I took to reliably produce errors with the server/client setup we had. Unlike most of our repositories, the Playground repo has always been FSFS. The problem happened with our BDB repos as well.
The problem doesn't reproduce with the currently supported versions, nor with the older versions we tried to setup specifically to trigger the problem quoted here.
But it's easily reproduced here, and obviously is at other sites too.

Do you see the problem in all working copies, or just in certain scenarios? (E.g. multiple levels of added directories? Mixed revision copies? Etc. etc.)
I saw it in nearly every case. There were rare occasions when the add/commit would just work, but in the majority of cases it would fail.

                Bert

From: JANIKOVIC Jan [mailto:jan.janikovic_at_power.alstom.com]
Sent: dinsdag 24 september 2013 12:51
To: users_at_subversion.apache.org
Subject: Problem with adding files in SVN 1.8.0+. Is it in the tracker already?

Hello,

There seems to be a problem with the TortoiseSVN1.8.0+, which returns a server conflict when a new file is attempted to be added. We observed the problem only when adding files to the server running SVN1.5.5. No problems were observed when adding files to our second server, running SVN 1.7.x. There are further posts about this issue on the Internet, such as https://groups.google.com/d/topic/tortoisesvn/cGoClRBMCPc/discussion
or
https://groups.google.com/d/msg/tortoisesvn/NggY3JzVJIY/gdEklFV2vLgJ

Is this issue already in the Subversion tracker (http://subversion.apache.org/reporting-issues.html)? If yes, could you please tell me the issue number

Kind regards
Jan

Jan Janikovic
ALPRO Implementation Specialist
Regards,

Geoff

--
Apologies for the auto-generated legal boilerplate added by our IT department:
- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files.