Hey thanks for the response. I guess this is something we should look
at more from the ASF infrastructure side.
Alex
On Mon, 2004-07-05 at 10:27, Ben Collins-Sussman wrote:
> 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 21:26:10 2004