Bug#270693: "svnadmin dump | svnadmin load" cycle not working due to 2GB limit

[Philip Martin]

Peter Samuelson <peter at p12n.org> writes:

> Yes, but more importantly, if we upgrade to libapr1 we break
> mod_dav_svn.  It needs to use the same apr that apache is using.  Thus
> we will upgrade to libapr1 when apache 2.2 hits Debian.  I am told
> apache 2.2 is coming to Debian "experimental" Real Soon Now.  How soon
> after that it gets to unstable, none can say.
>
> Not much we can do other than follow the apache group here.

Is there a Subversion packaging problem ahead?  If libsvn0 starts to
use libapr1 this will change the ABI of libsvn0 and any package built
against the existing libsvn0 ABI may not work correctly with the new
libsvn0.  Can Debian continue to call it libsvn0 if it's no longer
compatible with older versions of libsvn0?  I suppose Debian could
rebuild all the Debian packages that use libsvn0, but that doesn't
solve the problem for non-Debian binaries.  I suspect the libsvn0 name
will have to change, much like a C++ ABI transition.

-- 
Philip Martin