> I had a checked out copy created by svn 1.6; after updating the subversion > package to 1.7.5, it insisted on running "svn upgrade", which I did. > > $ svn st > ! gif/mobile > > Trying to run "svn log" on this directory causes svn to segfault:
Huh. Can you reproduce this? I mean, do you have a backup of the old working copy from before 'svn upgrade', or can you recreate one? It seems clear that the 'svn upgrade' went wrong somehow. If you can't reproduce the problem easily, can you make your current working copy available to me or other Subversion developers? E.g., a tarball on an http server would be fine. From that we could probably figure out why 'svn log' crashes, and _maybe_ work backward to how 'svn upgrade' got the working copy into that state in the first place. Thanks for the report, Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
