Bug#335455: Progress

[Peter Samuelson]

[Michael Biebl]
> is there any progress with this bug? I got a package which depends on
> libsvn0-dev and wanted to upload a new version. Unfortunately the
> db4.2<>db4.3 conflict makes it impossible.

We've got a db4.3-enabled subversion pretty much ready to go, *except*
for tracking down a simple and reliable procedure for upgrading one's
old svn repositories, so we can document it.

I *really* don't want to mess up the documentation on this one: it's
very important that people who have upgraded subversion don't suddenly
find themselves unable to read or write their old repositories - or,
worse, mess up their old repositories further by following our
instructions.

I'll look at the issue again tonight when I get home.  The last advice
I received didn't work in my tests.

Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/attachments/20051109/9b88c246/attachment.pgp