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

Re: Upgrade woes

From: Sander Stoks <sander_at_stoks.nl>
Date: 2003-09-14 23:31:41 CEST

Ben, Garrett, thanks for your responses.

> Garrett Rooney <rooneg@electricjellyfish.net> writes:
> > > svn: PROPFIND of /: 405 Method Not Allowed
> And really, this looks the standard error you get when there's a
> permissions problem. (Apache doesn't have complete r/w access to the
> repos/db/ files.) What does the Apache error log say?

This was an interesting hint. I saw the following error:

"bad database version: got 3.1.17, should be at least 4.0.14"

So I probably built with the wrong BerkeleyDB version. I did a make
clean and a new configure with the following switches:

./configure --with-aspx --with-zlib --with-berkeley-db=/usr/local/

and a remake. I removed my new repository, created a new one and
loaded the dumpfile again. It seemed to work, but I get exactly the
same error :-( I see that the exact version of BerkeleyDB I have is
4.0.1a - I guess that's not 4.0.14, but still not 3.1.17, so I wonder
why my configure didn't pick that up. I see the path correctly
included when making. Any help there? The path is correct; my /usr/
local/BerkeleyDB4.0 has include, bin, and lib subdirs (and doc).

> And yes, if your server is 0.29, your client can only *safely* be
> 0.28
> or 0.29. You better upgrade your client.

The reason I postponed this is because my client runs on BeOS, and the
configure support there is not working "out of the box". I tried
though, and although it fails later on in the build process when
linking libsvn_wc (with "undefined reference to
`svn_wc__remove_wcprops'" and a load of others), but at that point the
actual svn binary _has_ been built, and runs. The problem there is
that it crashes when I type "svn log", in svn_path_join
(the call stack is this:

segment violation occurred
+003b 80048347: * 028b movl (%edx), %eax
   frame retaddr
fd0011dc 8003902f auth_file_path + 0000003f
fd001220 800390ce svn_config_read_auth_data + 0000002a
fd001250 8002981f get_creds + 0000009f
fd00128c 80029ab2 simple_first_creds + 00000046
fd0012c4 80037b2a svn_auth_first_credentials + 0000009e
fd001304 800763ca request_auth + 000000a2
fd001330 80082cf8 get_credentials + 00000038
fd001350 80082d5e basic_challenge + 0000005e
fd001484 80084406 auth_challenge + 0000039e
fd0014c4 80084744 ah_post_send + 000000ec
fd0014f0 8008aefd ne_end_request + 00000071
fd001518 8008af8b ne_request_dispatch + 00000047
fd001530 80090e98 svn_ra_dav__parsed_request + 00000254
fd001584 8008efa7 svn_ra_dav__get_props + 00000247
fd00161c 8008f061 svn_ra_dav__get_props_resource + 00000099
fd001654 8008f1fb svn_ra_dav__get_starting_props + 00000033
fd001680 8008f2ca svn_ra_dav__search_for_starting_props + 000000c2
fd0016c4 8008f41e svn_ra_dav__get_baseline_props + 0000002e
fd00170c 8008f5ea svn_ra_dav__get_baseline_info + 0000003a
fd00174c 80080a2b svn_ra_dav__get_log + 000001af
fd0017cc 80027d2c svn_client_log + 000003dc
fd001844 80018c5a svn_cl__log + 000001d6
fd001898 8001a00d main + 0000106d
fd001af4 800165d5 _start + 00000061

I get the same crash whether I simply type "svn log" or "svn log http:/
/". The old svn still works, but gives me

~/oaknix/kernel$ svn-0.15 log
sanders's password:

subversion/libsvn_ra_dav/util.c:81: (apr_err=175002, src_err=0)
svn: RA layer request failed
svn: PROPFIND of /: 405 Method Not Allowed

which is probably the DB problem.

Many thanks for your help,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 14 23:31:41 2003

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.