On Mon, 2003-01-20 at 14:22, Garrett Rooney wrote:
this has nothing to do with using ra_svn over ssh, it's just that we
removed the svn_repos_close function recently, and you've got some
binary that's still looking for it. did you copy over a new svnserve
binary? how about all the various libraries (if you're compiling
things dynamically linked)?
Thank you and Karl for your quick response. It was indeed an
environmental issue. I make soft links to the important binaries (svn,
svnadmin and svnserve) directly from the build tree to ~/bin. This is
in order to avoid having to install stuff all over my HD and having to
deal with the commensurate lack of package management. Well, on the
server machine, I had actually made copies (or possibly hard links) of
the shell scripts instead of soft linking to them.
Once you fingered my environment, I took a closer look and quickly found
my problem.
BTW, if anybody wants RH 8.0 RPMs of a recent version of neon, I've
started maintaining them:
http://www.omnifarious.org/~hopper/technical/RPMs.html
I don't really have time to effectively keep up with the development
list here, but if someone bothers to point out when Subversion has begun
relying on a newer version of neon than I've packaged, I'll download the
new version and make a new package within a week or so.
Also, thanks a lot for adding in the ra_svn module and svn: schema. I'm
unwilling to deal with the headache of constantly insuring I have the
latest versions of apache and apxs installed. So, a version of
Subversion that doesn't rely on them actually enables me to play with it
and test it.
Thanks,
--
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (hopper_at_omnifarious.org http://www.omnifarious.org/~hopper)=
--
Received on Sat Oct 14 02:03:06 2006