Hi Chris, Upstream for SVN-Hooks looked into it so it seems to be triggered by a subversion bug in 1.9:
On Sat, Aug 22, 2015 at 01:09:32PM -0700, Gustavo Chaves wrote: > It seems that this is a bug on Subversion 1.9. I've just sent a > message to the us...@subversion.apache.org list with the subject > "svn (un)lock commands succeed when pre-(un)lock hooks fail on svn > 1.9" explaining it in detail. > > In summary, the "svn lock" and the "svn unlock" commands succeed on > svn 1.9 even if the corresponding hooks (pre-lock and pre-unlock) > fail. > > I think I'll have to check the subversion version and disregard > those two tests if I'm using svn 1.9.x. I wonder if we actually should reassign this to subversion and add an affects libsvn-hooks-perl, but as well add a workaround for this in our package so that if does not FTBFS. Regards, Salvatore
