[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnlook in pre-commit hook, delete operations copying directories

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Fri, 13 Jun 2008 22:59:52 +0200

Roman Fietze wrote:
> Hello,
> When I try to do a copy of the working directory to a new directory in
> the tags/ subdirectory, e.g.
> svn copy . http://svn.mydomain/svn/testproject/tags/V01.02.03
> and use svnperms.py inside the pre-commit hook, I cannot perform the
> copy. svnperms.conf was and is set up correctly, it never changed.
> E.g.:
> [groups]
> maintainers = fietze
> devall = fietze
> [testproject]
> trunk/.* = @devall(add,remove,update)
> tags/[^/]+/.* = @maintainers(add)
> branches/[^/]+/.* = @devall(add,remove,update)
> I get an error for every file added, because svnlook seems to report a
> 'D' and an 'A' operation for every copied file, no matter if using on
> the transaction or later on the revision (when I remove the pre-commit
> hook for testing this copy) which will cause an denied commit.
What happens here is that 'svn copy' takes the revision from your
working copy target ('.'), copies that revision in the repository
directly and then replaces all files that were changed on trunk after
that revision on the tag. If you (can) update your working copy
directory to HEAD this should not happen.

I'm not sure when it was introduced. Which version of the client where
you using previously?
> Example:
> Old days:
> A tags/V00.00.02/
> And today:
> A tags/V00.00.03/
> D tags/V00.00.03/Makefile
> A tags/V00.00.03/Makefile
> D tags/V00.00.03/bar.c
> A tags/V00.00.03/bar.c
> D tags/V00.00.03/foo.c
> A tags/V00.00.03/foo.c
> This must have changed, because we have those pre-commit hooks
> forever, and they had been working for a long time. When I issue an a
> "svnlook changed" on very old transactions the 'D' operation is not
> there. I do exacactly know when this changed, currently I'm running
> subversion-1.5.0-112.1 from the openSUSE 10.3 repositories.
If svnmerge.py would support specifying rules for 'replaced' items,
would that solve this issue for you?


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-13 23:00:23 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.