Bug#326079: subversion: bug marked as fixed in nmu still lives

Package: subversion Version: 1.2.3-0.1 Severity: grave Tags: experimental l10n Justification: renders package unusable Hi. My previous #316143 (co-merged with #323376) still applies as such: [EMAIL PROTECTED]:~/tmp/svn$echo $LANG [EMAIL PROTECTED] [EMAIL PROTECTED]:~/tmp/svn$svnadmin create svntes

Bug#316143: subversion: segfault when add a directory

= 0 unlink("a/.svn/lock") = 0 unlink(".svn/lock") = 0 munmap(0xb7d77000, 4096)= 0 exit_group(0) = ? The segfault disappeared. IMHO this bug can be closed or merged with #323376 -- Carl

Bug#316143: subversion: segfault (not due to libapr0) when add a directory

killed by SIGSEGV +++ > In any case, I'm assuming it's correct to tag this bug 'sid', since 1.2.0-1 > isn't in testing and this bug has only been reported against the new > version. I agree. I attached here add_log. HTH. Maybe the new upstream 1.2.1 is not affect

Bug#316143: subversion: segfault (not due to libapr0) when add a directory

Package: subversion Version: 1.2.0-1 Severity: grave Justification: renders package unusable Hi. I know the bug 266165 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266165). The behavior is the same but the segfault IMHO does not depend on libapr0 because it shows even using the local filesyst