You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Berwyn Hoyt <be...@brush.co.nz> on 2007/07/18 20:20:08 UTC

pre-commit doesn't output errors when moving files

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
The pre-commit script will not output an error on failure when you are
moving files.&nbsp; Client output looks like this:<br>
<br>
svn ci -m 'test"<br>
Adding: P:\mpledge\setup\ipstats.py&nbsp; <br>
Deleting: P:\mpledge\setup\traffic\ipstats.py&nbsp; <br>
Error: Commit failed (details follow):&nbsp; <br>
Error: MERGE request failed on '/trunk/setup'&nbsp; <br>
Error: MERGE of '/trunk/setup': 409 Conflict (<a
 class="moz-txt-link-freetext" href="https://svn.mpledge.com">https://svn.mpledge.com</a>)&nbsp;
<br>
<br>
I've got the server down to a very simple pre-commit script:<br>
&nbsp; #!/bin/sh<br>
&nbsp; echo test1<br>
&nbsp; echo test2 1&gt;&amp;2<br>
&nbsp; echo "running pre-commit $@" &gt;&gt;/var/log/svn<br>
&nbsp; exit 1<br>
<br>
Details:<br>
- The commit succeeds fine if I change the pre-commit script above to
exit 0.<br>
- The above script logs a line to /var/log/svn, so I know the script is
running fine.<br>
- The problem does not occur if I'm just changing a file, only when I
svn mv it (in this case, between directories)<br>
- I'm using https access through apache.&nbsp; The problem does not occur if
I check out the repository using "svn co <a
 class="moz-txt-link-freetext" href="file://">file://</a>..."<br>
- The server is runing debian sarge with svn (and mod_dav_svn.so)
version 1.4.2 (r22196).<br>
- This appears to have similar symptoms to a bug fixed in svn v1.3, but
there are no long times involved and it only fails on moved files so it
is different. See: <br>
&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext"
 href="http://subversion.tigris.org/issues/show_bug.cgi?id=2668">http://subversion.tigris.org/issues/show_bug.cgi?id=2668</a><br>
<br>
So, in summary, set up an https (may work for http) server and move a
file between directories and make sure there's something in it that
triggers an error in the pre-commit script.&nbsp; Can anyone else reproduce
this?<br>
<br>
Cheers,<br>
Berwyn<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; ">
<title>--</title>
<meta name="GENERATOR" content="OpenOffice.org 2.1  (Win32)">
<meta name="CREATED" content="20061130;17204690">
<meta name="CHANGEDBY" content="Berwyn Hoyt">
<meta name="CHANGED" content="20070111;12363553">
<style>
	<!--
		P.msonormal { margin-bottom: 0cm }
		A:link { color: #0000ff }
		A:visited { color: #800080 }
	-->
	</style>
<p><b><i>Berwyn Hoyt,</i></b>
<i>Senior Hardware Engineer:</i> <a href="mailto:berwyn@brush.co.nz">berwyn@brush.co.nz</a><br>
<b><i>Ph: </i></b>+64 3 359 2101; <b><i>Mobile:</i></b> +64 21 045
7830<br>
<b><i>Brush
Technology: </i></b><a href="http://www.brush.co.nz/">www.brush.co.nz</a><br>
</p>
</div>
</body>
</html>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org