> From: Sean Russell [mailto:email@example.com]
> Sent: 19 December 2001 03:35
> I guess it is time to bug the dev list.
> First off, I've been working on two distinct problems with SVN. Sander
> walked me through a persistent one, having to do with incompatible DB
> problems, which I'll write up; I've encountered it myself a few times, so I'm
> guessing others will too along the way.
It's something quite trivial, I'll post a patch to INSTALL to include the
sometimes needed extra info in section V.
For those who don't know: if apr-util links to a different version of
db than svn is linked to, the svn server will not be able to open a repos
(due to db incompatibility). So, at apache (or actually apr-util) configure/compile
time, you have to tell it where to find the db you want to use.
> The environment I'm running is the current Apache2 from CVS (as of today) and
> the same SVN (661, I believe).
> Anyway, copy has never worked for me; I've added the ServerName directive to
> the httpd.conf file, to no avail. The server error logs report:
> [Tue Dec 18 11:39:41 2001] [error] [client 184.108.40.206] Could not fetch
> resource information. [500, #0]
> [Tue Dec 18 11:39:41 2001] [error] [client 220.127.116.11] could not determine
> resource kind [500, #21050]
> [Tue Dec 18 11:39:41 2001] [error] [client 18.104.22.168] file not found:
> filesystem `/home/subversion/repos/db', revision `10', path
> `/rexml/tags/1.2.3' [500, #21050]
> on any sort of copy; I think this error was an attempted repos->repos copy.
> I've been told that cp requires a special apache configuration, but nobody
> can tell me, other than ServerName, what that is. Sander suggested I post to
> the collective for an answer.
Yes. I also said that you should paste the relevant portions of your
httpd.conf (so we can spot problems with it). And more importantly, you
should tell did to cause the error to appear. Paste your last [few if
relevant] commands you gave on the commandline (ad verbatim).
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Oct 21 14:36:53 2006