I can reproduce this with trunk.
Mark Eichin wrote on Tue, Aug 16, 2011 at 17:54:57 -0400:
> Ran across this while writing a "populate new repo" script, that used
> svn cp to copy a set of svn-hooks in place (by definition from one
> repo to another.) What happens is that when a file in the source repo
> (called "foreign" here) has svn:executable set, the working dir in the
> destination (called "local" here) looks right - ls -l shows the +x
> bits, svn proplist -v shows the property, even .svn/props-base
> mentions it. The commit, on the other hand, doesn't push it to the
> repository. This means that the local checkout is now a "persistent
> lie" (in that trying to set it there and commit it does nothing,
> because it's "already" set.)
So, it's definitely a bug *somewhere*.
> svn co $LOCAL_REPO/branch $PERFORM_COPY_WORKDIR/branch
> svn copy $FOREIGN_REPO/trunk/program $PERFORM_COPY_WORKDIR/branch/copied-program
Is this documented to work?
Received on 2011-08-17 00:23:39 CEST