On 7/23/07, Ed Wittmann <ewittmann@combinenet.com> wrote:
> Hi there:
>
> We have a subversion setup here with the
> standard /trunk, /branches, /tags.
>
> In order to insure that tags don't get modified after commit, we have,
> via apache config, limited the HTTP commands that can be applied to
> the /tags to the following:
>
> LimitExcept "GET PROPFIND OPTIONS REPORT COPY"
>
> This works just fine unless you're trying to create another tag from a
> tag:
>
> svn cp https://svn/repos/software/tags/tag1
> https://svn/repos/software/tags/tag2
>
> This fails because of the following (excerpted from apache logs):
>
> 127.0.0.1 - someuser [23/Jul/2007:12:12:02 -0400]
> "MERGE /repos/software/tags/ HTTP/1.1" 403 523
>
> If I open up /tags for MERGE, then I won't be able to ensure that tags
> remain inviolate.
MERGE is, as far as I understand, the command to integrate the DeltaV
workspace with its baseline. I.e. it's the step to finalize the copy.
The other option is to set up svnperms.py
(http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/) and make
it reject commits which do anything other than add items to your tags
dir...
> Why do I see a merge here at all? The "COPY" I understand... Is there a
> way around this?
Best is probably to set up svnperms.py.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 23 19:53:13 2007