Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of BKWalker@drbsystems.com
 designates 12.196.88.136 as permitted sender)
From: Brenden Walker <BKWalker@drbsystems.com>
To: "users@subversion.apache.org" <users@subversion.apache.org>
Subject: RE: SVN copy that worked in 1.8.0 now fails with (424 Failed
 Dependency)
Thread-Topic: SVN copy that worked in 1.8.0 now fails with (424 Failed
 Dependency)
Thread-Index: Ac6Tg7Pi9uTfihAaTku4mKVXJ/BGog==
Date: Wed, 7 Aug 2013 15:41:35 +0000
Message-ID: <6DF864426572664E96691EF01A78725919B6C3@DSIMail.drbsystems.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> -----Original Message-----
> From: Brenden Walker [mailto:BKWalker@drbsystems.com]
> Sent: Wednesday, August 07, 2013 11:27 AM
> To: users@subversion.apache.org
> Subject: SVN copy that worked in 1.8.0 not fails with (424 Failed Depende=
ncy)
>=20
> svn: E175002: Adding directory failed: COPY on
> /svn/Development/!svn/rvr/7020/Trunk/Projects/SiteWatch (424 Failed
> Dependency)
>=20
> This is part of our build process which hasn't changed and worked prior t=
o
> updating to 1.8.1 yesterday (Visual SVN Server).  I tested copying some o=
ther
> paths and that works, the path in question has externals defined which I
> suspect may have something to do with this?
>=20
> I don't see anything in the release notes that would seem relevant.
>=20
> I'm going to do more testing on my end, try to figure out what happened.
> Any suggestions?
>=20
> Thanks!

Follow up.. I was mistaken on the timing for this, it may have been introdu=
ced when we updated to 1.8.0

I can copy many other things, I have it narrowed down to 2 particular paths=
 under the main folder being copied.    So far I haven't found anything unu=
sual about these paths, no unusual properties (externals or the like).