On 24 March 2014 01:21, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Daniel Shahaf wrote on Sun, Mar 23, 2014 at 02:34:35 +0000: >> sebb wrote on Sat, Mar 22, 2014 at 01:28:33 +0000: >> > To reproduce the problem, start as follows: >> > >> > svn co http://dist.apache.org/repos/dist/release/commons/dbcp/@4582 >> > >> > Then apply the following revisions in order: >> > >> > 4583 >> > 4586 >> > 4588 >> > 4592 >> > 4593 >> > 4599 >> >> I can't reproduce an error with latest svn-1.8.8 from ports on FreeBSD 9.1. > > I can reproduce Andreas' and Philip's results. I missed them on first > scan because the OP specifically reported a conflict, so I only looked > for conflicts. And I know 'svn up' reports conflicts, so I didn't run > 'svn st'... > > I don't want to sound like I'm shifting the blame (and I'll readily > admit that I was short on time when I did the checkout/update dance), > but that's exactly why including output transcripts in bug reports is a > good idea.
Well, I got multiple conflict dialogs on both FreeBSD and WinXP when using "svn up -r nnnn" for some values of nnn I thought it would be the same for others. > Daniel
