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

Re: Re: Is subversion ready for primetime

From: Joseph Silverman <yossie_at_laszlosystems.com>
Date: 2005-02-01 00:23:26 CET

First and foremost, I must apologize for the subject line. This was a
"reactionary" act rather than well thought out one. The primary
motivation is an extended frustration trying to get subversion to do
what I want it to do - that, and a bad case of foot-in-mouth.

As to why I am frustrated ..

I am tasked with creating a perforce -> subversion gateway that will
allow my company to continue to use perforce internally (for various
reasons, non-the-least of being a large number of automated processes
that use perforce) and yet allow the world at large to use subversion
to access our open source product (in "read-only" mode, for now).

I am doing this with a submit trigger in perforce that will (based on
the change description) figure out what svn commands to issue to keep a
svn repository in step with a perforce depot. This is, currently,
intended to be a one-way gateway.

Some of the things I am getting hung up on are:

Trying to configure Apache and svn to work together and finding that it
is not particularly easy, beyond the "basic" setup described in the
various online docs. I will investigate using the mod_authz_svn
module. This is the most recent hangup and the one that trigged my ill
considered subject: line.

It is a rather simple matter to lock up a svn working copy in such a
way that will throw both the client and server sides into an infinite
and somewhat cpu intensive loop (just kill the a svn command - pretty
much any svn command - with -9!) - svn cleanup goes into a loop at this
point as well. I haven't figured out how to back out of this short of
trashing the svn working copy all together and co'ing out a new one.
This has caused me no end of grief.

To be sure, svn 1.1 and 1.2 requires a recent level of apache 2.
Trying to find rpm's for not-latest version of linux for Apache, and
all it's modules, has been rather impossible, in fact. So I have
resorted to a "barebones" Apache server which is ONLY used by svn
(simplifying this somewhat and allowing me to proceed).

Most subversion error messages are a bit on the uninformative side
(e.g. the one that triggered the original email!) - and while it might
be unfair to complain about this given that it is opensource, it does
make it harder for a first-time user (me) to get up to speed with it.

For the life of me I can't figure out how to merge back to the
"original", a file that was "copy"ed from it and then changed, in a
way that is similar to doing so in perforce. Perhaps this is simply
not possible in subversion.

- Yossie

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 1 00:25:46 2005

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.