That's exactly the problem. In SVN 1.6 I was able to run concurrent SVN
updates on different directories. Their separate databases were updateable
separately. In 1.7, this is no longer possible.
I would be happy to revert our application to using SVN 1.6, except that
1.6 has a problem, as explained at the root of this thread. The original
resolution recommended by you guys was to switch to 1.7, but we cannot do
that because of these newly found concurrency issues.
Can we simply fix the original issue in SVN 1.6 instead?
On Thu, Sep 5, 2013 at 12:40 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> You should be able to update from any path. I’m not sure if they can run
> “concurrently” though. ****
>
> ** **
>
> svn [PATH…]****
>
> ** **
>
> BOb****
>
> ** **
>
> ** **
>
> *From:* Mihai Danila [mailto:viridium_at_gmail.com]
> *Sent:* Wednesday, September 04, 2013 3:13 PM
> *To:* Philip Martin
> *Cc:* dev_at_subversion.apache.org
> *Subject:* Re: SVN update of child ignores files if preceded by update
> --depth immediates****
>
> ** **
>
> Philip,****
>
> ** **
>
> We have upgraded our working copies to SVN 1.7, but, unfortunately, the
> single ".svn" directory per working copy paradigm used by SVN 1.7 prevents
> us from running concurrent updates to different areas of our working copy.
> We get errors and locked working copies.****
>
> ** **
>
> Is it possible to fix SVN 1.6 so that we might use it and achieve our goal
> of updating different portions of the working copy concurrently? Or, is
> there some way to run concurrent updates on different areas of an SVN 1.7
> working copy that we are not aware of?****
>
> ** **
>
> Mihai****
>
> ** **
>
> ** **
>
> ** **
>
> On Mon, Aug 12, 2013 at 5:15 PM, Mihai Danila <viridium_at_gmail.com> wrote:*
> ***
>
> Thank you Philip. We will upgrade to a newer SVN version.****
>
> ** **
>
> ** **
>
> On Thu, Aug 8, 2013 at 1:34 PM, Philip Martin <philip.martin_at_wandisco.com>
> wrote:****
>
> Mihai Danila <viridium_at_gmail.com> writes:
>
> > With Subversion 1.6.5, 1.6.13, and I believe Subversion 1.7 also, I
> noticed
> > the following bug, which I first asked about on StackOverflow about and
> had
> > independently confirmed (
> >
> http://stackoverflow.com/questions/18114102/strange-svn-behavior-missing-files-when-using-depth-immediates-followed-by-dep
> > ).
> >
> > I will copy straight from there.
> >
> >****
>
> > - Repository:
> > - Revision 0: empty
> > - Revision 1: dir1/f1.txt
> > - Revision 2: dir1/f1.txt, dir1/f2.txt, dir2/f3.txt
> >
> > Your typical, right?
> > ------------------------------****
>
> >
> > Now for the strangeness. I'm running these commands in the WC root.
> >****
>
> > - Commands
> > 1. svn update -r1 - Update to revision 1 is successful, working
> copy
> > looks good.
> > 2. svn update --depth immediates - All good, dir2 gets created and
> is
> > empty, no other changes.
> > 3. svn update dir1 --set-depth infinity - SVN says OK, but****
>
> > dir1/f2.txt just
> > won't pop up in my working copy.****
>
> > 4. svn update - just cause I'm getting anxious - nothing,****
>
> > dir1/f2.txt still
> > wont pop up.****
>
> > 5. svn update -r1 - Error: dir1/f2.txt is not under version control
> > (WHOA?)
> > 6. svn update - Now I get dir1/f2.txt in.
>
> svnadmin create repo
> svnmucc -mm -U file://`pwd`/repo mkdir D1 put repo/format D1/f1
> svnmucc -mm -U file://`pwd`/repo put D1/f2 mkdir D2 put repo/format D2/f3
> svn co file://`pwd`/repo_at_1 wc
> svn up --depth immediates wc
> svn up --set-depth infinity wc/D1
> svn st -v wc
>
> With 1.7 and 1.8 the status shows
>
> 2 2 pm wc
> 2 2 pm wc/D1
> 2 1 pm wc/D1/f1
> 2 2 pm wc/D1/f2
> 2 2 pm wc/D2
>
> With 1.6 the status shows
>
> 2 2 pm wc
> 2 2 pm wc/D2
> 2 2 pm wc/D1
> 2 1 pm wc/D1/f1
>
> So this is a bug in 1.6 that is fixed in 1.7 and 1.8.
>
> --
> Philip Martin | Subversion Committer
> WANdisco | Non-Stop Data****
>
> ** **
>
> ** **
>
Received on 2013-09-05 19:05:58 CEST