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

Re: [svn] commit failure reported on success

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-05 16:27:27 CEST

On Sun, 2004-07-04 at 02:27, Alex Karasulu wrote:
> Ok this is it I promise :-). More info again.
> The svn commit email failed to go out. I know this for sure (rather than
> a delay being the issue) because I just generated revision 22521 which I
> just recieved: 22520 on the failed commit never made it out the door.
> This may be important maybe not.

Alex, everything that happened to you is perfectly explainable.

1. Your client sent a commit.

2. Apache applied your commit to the repository.

3. Apache started to run a post-commit hook to send email, but (for some
reason), it looks like this hook script never returned, or took
incredibly long to complete.

4. The client (libneon) timed out waiting for a server response.

Therefore, (1) no commit mail went out, (2) your client printed an
error, and thinks the commit never happened, (3) the repository has the
new revision anyway. When you try to update, you'll get conflicts,
because the server is trying to send the same changes that already exist
as 'local mods' in your working copy. It's probably best to just toss
your working copy, or 'svn revert -R' to get rid of all your mods.

The only real question here is why the hook script didn't return.
Perhaps your 'post-commit' script should run another script
backgrounded? That's what most people do.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 5 16:32:05 2004

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.