Control: reopen -1
Control: found -1 1.9.4-1
On 2008-10-14 18:12:07 +0200, Andreas Beckmann wrote:
> Also the svn command still running is not interruptable by any other
> means (more ^C or signals) except for SIGKILL (which sometimes results
> in a repository that can't even be fixed by 'svn
On 2016-01-27 14:55:55 +0100, Vincent Lefevre wrote:
> Package: subversion
> Version: 1.9.3-2
> Followup-For: Bug #50
>
> Still occurs. Backtrace:
[...]
Note: here this wasn't really due to a slow connection, but there was
some problem with the server, which could be joined, but didn't
Package: subversion
Version: 1.9.3-2
Followup-For: Bug #50
Still occurs. Backtrace:
Thread 1 (Thread 0x7f68a0838780 (LWP 23588)):
#0 0x7f689f38b800 in __read_nocancel () at
../sysdeps/unix/syscall-template.S:81
No locals.
#1 0x7f689f5b2836 in apr_file_read () from
On 2008-10-14 18:12:07 +0200, Andreas Beckmann wrote:
if I press Ctrl-C during a svn operation, svn often does not terminate
properly.
This problem has just occurred on one of my machines, also with
subversion/1.5.1dfsg1-1.
Here's what a strace -p gives when I type Ctrl-C several times:
Package: subversion
Version: 1.5.1dfsg1-1
Severity: normal
Hi,
if I press Ctrl-C during a svn operation, svn often does not terminate
properly.
For instance, I may want to abort a 'svn update' that retrieves a lot of
updates over a slow connection. Svn does somehow stop processing the
update
5 matches
Mail list logo
