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

Re: pre-revprop-change stdin wrong?

From: <kmradke_at_rockwellcollins.com>
Date: Thu, 12 Feb 2009 16:55:08 -0600

Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote on 02/12/2009 12:31:30 AM:
> Ryan Schmidt wrote on Wed, 11 Feb 2009 at 22:42 -0600:
> > On Feb 11, 2009, at 18:15, kmradke_at_rockwellcollins.com wrote:
> >
> > > Using svn 1.5.1 FSFS and the http protocol, I created a pre-revprop-

> > > change hook
> > > script like this:
> > >
> ....
> > > subversion/libsvn_ra_neon/fetch.c:1175: (apr_err=175002)
> > > svn: DAV request failed; it's possible that the repository's pre-
> > > revprop-change hook either failed or is non-existent
> > > subversion/libsvn_ra_neon/props.c:1151: (apr_err=175008)
> > > svn: At least one property change failed; repository is unchanged
> > > subversion/libsvn_ra_neon/util.c:206: (apr_err=175002)
> > > svn: Error setting property 'log':
> > > Revprop change blocked by pre-revprop-change hook (exit code 1)
> > > with output:
> > > This stdin is from pre-revprop-change:
> > > -----
> > > old log message
> > > -----
> > >
>
> Just wondering, is it possible that the hook is called *twice* --- once
> with the old log message, once with the new one?

Just confirmed this is the case, but only when using the http:// protocol,
not file://. Very odd.

The double hook call was reported over a year ago:

http://subversion.tigris.org/issues/show_bug.cgi?id=3085

(I just didn't read far enough to see the output from the first
 run is discarded by neon/serf and it is the second run that
 contains the old message as stdin and is reported.)

Kevin R.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1147678

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-13 03:37:14 CET

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.