svn server support for "gvn submit" command

[ryanc...@gmail.com]

Hi all,

After a couple hours of setup, I seem to have every critical feature
of "gvn" working except for the the last, most important command: "gvn
submit". I'm seeing this error:

>gvn submit -c e7c2
Submitting [user]/e7c2@20
gvn submit failed:
gvn: Server doesn't support setting arbitrary revision properties
during commit

It seems obvious form the error message that I'm missing this feature
on the server. I noticed the comment in the Windows install guide
that gvn "uses as-yet-unreleased features in Subversion". I'm using
the provided windows svn package for my client (subversion-1.5.0-rc5-
windows-xp-i386.zip). However, our server is on RedHat and is running
"CollabNetSubversion-server-1.4.2-8".

Can anyone clarify if I will also need to install a "trunk" copy of
SVN on our server as well, or whether there is a way to activate the
feature of "arbitrary revision property setting" on the collabnet-
packaged svn server? I had a somewhat similar problem earlier (with
"ack") that was solved by me activating the "pre-revprop-change" hook
on the server, but I can't find a workaround for this issue.

Since our SVN server is in production, I'm not real keen about having
to sub in a new version (and migrate any config, hooks, etc.).
However, I'm willing to do it if I'm relatively sure that doing so
will fix this problem.

Thanks for any help,
Ryan

[e...@google.com]

ryanc...@gmail.com writes:

> After a couple hours of setup, I seem to have every critical feature

Ouch. Sadly, I'm not surprised. Our biggest problem is lack of
documentation, but if you have criticisms to share, don't hold
back :).

> >gvn submit -c e7c2
> Submitting [user]/e7c2@20
> gvn submit failed:
> gvn: Server doesn't support setting arbitrary revision properties
> during commit

> windows-xp-i386.zip). However, our server is on RedHat and is running

> "CollabNetSubversion-server-1.4.2-8".
>
> Can anyone clarify if I will also need to install a "trunk" copy of

This feature is new in 1.5.0, which (*crossing fingers*) will be
out very soon now. So, you won't need to install "trunk".
Collab.Net is providing RPMs for the release candidates, and I'm
sure RPMs for the final release will follow soon.

> Since our SVN server is in production, I'm not real keen about having
> to sub in a new version (and migrate any config, hooks, etc.).
> However, I'm willing to do it if I'm relatively sure that doing so
> will fix this problem.

It will certainly fix the problem, but yeah, upgrading the server
may not be what you want to do right now. There is another
option. I've just filed an issue about it:
http://code.google.com/p/gvn/issues/detail?id=69

[ryanc...@gmail.com]

Thanks again for the quick and helpful response. As I mentioned, I
don't mind putting up a new svn server version if it will fix the
problem. Knowing that I can use an RPM makes the idea much more
palatable, also. I will give this a try tomorrow and write back to
this thread. I don't think I'll need your other workaround, but I'll
let you know.

BTW, regarding the install process... it was a little long, but no
worries! Every project takes a few years to mature in that area. :)
For anybody revising the install guide, I think the main things that
slowed me down were

a) Synching the various tool versions. I put in python 2.5 first, then
RTFM a little closer, and decided to just use 2.4 to avoid traveling
an "unknown" path. Also I had to replace my existing svn client,
change PATH vars, etc. I don't know if there is anything that can be
changed in the install guide to help this, but nevertheless, this
process took awhile. I was being extra careful since I'm vetting the
whole install process for my entire dev group.
b) Finding the workaround for the "svn ack" error (install the pre-
revprop-change hook on the server).
c) Finding the workaround for this "svn submit" error [see below].

Maybe that will help future users. Thanks again.

--Ryan

On May 29, 6:45 pm, e...@google.com wrote:

[David Glasser]

I try to use Python 2.5; if it doesn't work that's a problem.

--dave

--
David Glasser | gla...@davidglasser.net | http://www.davidglasser.net/

[e...@google.com]

ryanc...@gmail.com writes:

> a) Synching the various tool versions. I put in python 2.5 first, then
> RTFM a little closer, and decided to just use 2.4 to avoid traveling
> an "unknown" path.

It should probably work, but there may be an issue with the
Subversion Python binding being built with 2.4 but loaded into
2.5. I'm not sure.

> Also I had to replace my existing svn client,
> change PATH vars, etc. I don't know if there is anything that can be
> changed in the install guide to help this, but nevertheless, this

Changing PATH is in the instructions, though maybe it's not
obvious enough that you have to do it (or just always use gvn and
never svn directly).

> b) Finding the workaround for the "svn ack" error (install the pre-
> revprop-change hook on the server).
> c) Finding the workaround for this "svn submit" error [see below].

Both these belong in the instructions; I'll add them. I don't
suppose you still have the error messages around? It would save
me the trouble of reproducing them :).

> Maybe that will help future users. Thanks again.

Yes, it's helpful, thanks.

[ryanc...@gmail.com]

A couple notes on this older thread.

First, updating our SVN server to CollabNet SVN Server 1.5 (RC 9, I
think) fixed the gvn submit command, which was the original problem in
this thread. Great, thanks!

Second, here is the error for the "gvn ack" command you asked for [see
above]. Sorry for the delayed response; I hope you didn't have to
reproduce in the meantime :)

--------snip------------
C:\>gvn ack n4e7
gvn ack failed:
gvn: Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook
--------snip------------

Cheers,
Ryan