SVN: possible repository corruption with the FSFS backend

[Peter Samuelson]

> The issue has been fixed in Subversion 1.4.2. However, we use Debian
> Sarge on our production server, although not the official 1.1.4, but
> a backported 1.3.2. Backporting 1.4.2 to Sarge seems to be a huge
> (although not impossible) task for me. Are there any chances that
> 1.4.2 or the bugfix itself will be somehow backported?

We have a sarge backport of 1.4.2 but I haven't advertised it as I
haven't got around to finding a sarge machine to test it on.  I've done
some testing in a chroot, but not quite enough to be confident.

My current build is available at http://p12n.org/tmp/svn142-sarge/.
The one regression I know about from the sarge packages is the lack of
a 'svn_load_dirs' script in the subversion-tools package - this is for
licensing reasons.  This breaks the svn-buildpackage program.

If you'd like to test this build a bit and let us know how it works, I
can then propose it for backports.org.

Thanks,
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/20061221/170c8ab3/attachment.pgp