Apache Allura™

Forge software for hosting software projects

Brought to you by: alexluberg, brondsem, ccruz, deshani, and 11 others

#4533 svnsync not supported / missing pre-revprop-change hook

Milestone: v1.0.0

Status: closed

Owner: nobody

Labels: migration (63) sf-1 (616)

Component: General

Reviewer: nobody

Updated: 2015-08-20

Created: 2012-07-12

Creator: Anonymous

Private: No

Originally created by: laha

I just migrated to Allura, and my svn repo now has its rev0 revprops that control svnsync pointing at the wrong things.
I tried doing a propedit on them, but get the following error:

svn: DAV request failed; it's possible that the repository's pre-revprop-change hook either failed or is non-existent
svn: At least one property change failed; repository is unchanged
svn: access to '/p/safir/svn/!svn/bln/0' forbidden

This is very annoying! If I had known I would certainly not have migrated! Is it possible for you to add the default pre-revprop-change hook that you had in Classic? If that is done then I'll be able to fix the incorrect properties myself.

Discussion

Anonymous - 2012-07-12

Originally by: laha

Sorry for the harsh tone... I was a bit annoyed when I wrote the ticket.
I do understand that this is Beta software, so these things happen.
But I would be really happy if this could be resolved soonish.
Let me know if there is anything I can do to help or test this out.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2012-07-12

Originally by: laha

Okay, more apologies forthcoming:
I realized that this might have been the wrong place to post this problem, so I also posted it at
https://sourceforge.net/apps/trac/sourceforge/ticket/26595

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-07-13

Sorry for the trouble, Lars. The project upgrade process does not handle hooks currently. I'd recommend that you continue to use the old SVN repo, since that is unchanged and still works. Once we get hooks and revprops working well, you can import your "classic" SVN repo into the new system and set up the hooks/revprops then.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-07-13

labels: --> migration

milestone: limbo --> forge-backlog
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2012-07-13

Originally by: laha

Thanks for the tip, but when I try svnsync to that repo I get the following:

svnsync: DAV request failed; it's possible that the repository's pre-revprop-change hook either failed or is non-existent svnsync: At least one property change failed; repository is unchanged svnsync: Server sent unexpected return value (403 Forbidden) in response to PROPPATCH request for '/svnroot/safir/!svn/bln/0'

So I guess either something has happened to the hooks or to the permissions in the old repo.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-08-29

size: --> 1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-07

Hooks (including pre-revprop-change) can be changed on the new SVN repos by project admins. https://sourceforge.net/p/forge/community-docs/Subversion/#adding-an-svnnotify-hook explains how to access them (although it is mostly talking about an svnnotify hook).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2012-09-07

status: open --> closed

milestone: forge-backlog --> forge-sep-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2012-09-30

Originally by: laha

Excellent! Sync is working like a dream! Although I didn't have to do anything, just worked for me...
Thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.