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

RE: Issues with Subversion and ViewCVS

From: Alex Brown <abrown_at_diginexus.com>
Date: 2003-06-16 19:40:15 CEST

You are right that I was bringing up two separate issues in the message.

You were also right on the permission issue. I have a convoluted Samba
setup and it had some permission issues.

As far as ViewCVS, subversion is in the path as far as I can tell. I
even explicitly defined it (After your first email).
I also just upgraded to Subversion 0.24.

Now I have in my viewcvs.conf:

svn_roots =
        svn : /home/svnroot
default_root = svn
rcs_path = /usr/local/bin


-----Original Message-----
From: cmpilato@collab.net [mailto:cmpilato@collab.net]
Sent: Monday, June 16, 2003 12:36 PM
To: Alex Brown
Cc: dev@subversion.tigris.org
Subject: Re: Issues with Subversion and ViewCVS

"Alex Brown" <abrown@diginexus.com> writes:

> I now appear to have a few issues with my Subversion repository (0.23)

> and View CVS:

I think you may have a combination of things working against you. The
./svn/lock issues have nothing to do with ViewCVS -- ViewCVS is a
repository browser, and if not completely misconfigured, has nothing to
do with working copies. The 'no module named svn' error is an
indication that your Subversion bindings are probably either not
properly installed, or not visible to the viewcvs.cgi script. As for
the .svn/lock errors, that looks like a permissions problem.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 16 19:40:57 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.