On Sat, Jan 22, 2005 at 12:12:44PM -0600, Ben Collins-Sussman wrote:
> >Actually, I've just read this closer. It's about /switching/ from 0.95
> >to 1.0. In that case, would it help to recreate the repository from a
> >dump file using my currently installed version? Surely that should
> >sort
> >things out. Or are there libapr dependencies in the dumpfile?
>
> Nope, the whole point of the dumpfile is that the data is timeless and
> portable, so you can switch between versions of svn, fs backends, db
> schemas, etc. Give it a shot, see what happens.
Ok.
% ldd =svnadmin | grep apr
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9 (0x280f6000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28326000)
% svnadmin create /tmp/testrepos
% zcat /local/backup/svn/svndump-private-2005-01-22.gz | svnadmin load /tmp/testrepos
...
------- Committed revision 495 >>>
% svn co file:///tmp/testrepos/trunk
...
A trunk/etc/cricketconf/cricket-config/systemperf/ppe
zsh: segmentation fault (core dumped) svn co file:///tmp/testrepos/trunk
So sadly, it still breaks even on a brand new repository. Retrying with
an fsfs repository instead of a bdb one produces exactly the same
results.
What's disconcerting is that when I compiled the port with the
WITH_MAINTAINER_DEBUG option[1], the problem goes away. I'll try
recompiling with just "-g" in CFLAGS, so at least I can get some useful
info out of gdb...
Thanks,
-Dom
[1] Enables --enable-maintainer-mode and --enable-maintainer-mode and
puts "-g" into CFLAGS.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jan 22 19:45:53 2005