Package: subversion Version: 1.8.10-2 Severity: important Tags: upstream Dear Maintainer,
I just discovered that subversion no longer works if a working copy contains multiple filesystems. I use subversion across my entire file system to track changes in various places (with lots of svn:ignores for /usr, /var, etc) That has worked wonderfully for years, but today, I ran: svn commit on a modified file, and it failed saying something about a hard-link across devices. My entire checkout is now hosed, and svn cleanup refuses to fix it. The developers appear to be saying that they will not fix it, and the only choice is to downgrade to 1.6 (unsupported). http://mail-archives.apache.org/mod_mbox/subversion-users/201402.mbox/%3c52f020b8.4020...@reser.org%3E -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages subversion depends on: ii libapr1 1.5.1-3 ii libaprutil1 1.5.3-3 ii libc6 2.19-11 ii libldap-2.4-2 2.4.39-1.1+b1 ii libsasl2-2 2.1.26.dfsg1-11 ii libsvn1 1.8.10-2 subversion recommends no packages. Versions of packages subversion suggests: ii db5.3-util 5.3.28-6 ii patch 2.7.1-6 ii subversion-tools 1.8.10-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
