Your message dated Tue, 3 Apr 2007 21:02:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#289707: rsync: crashes on partial file transfer
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: rsync
Version: 2.6.3-2
Severity: normal
I have a shell script (checkiso) that relies on downloading a partial
file. The script used to work at least until the end of April (I
upgrade regularly from testing). Since then I have not used it until
today, when I discovered that rsync is broken. To reproduce:
$ ulimit -S -f 3300
$ rsync --quiet --partial
ftp.es.debian.org::debian-cd/3.0_r4/alpha/debian-30r4-alpha-binary-1.iso .
rsync: connection unexpectedly closed (53 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(359)
rsync dumps core and leaves an incomplete downloaded file whose name
begins with a dot. Since the --partial option is used, it should rename
it to the target file, and obviously should not dump core and print an
error.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-rc3-pr-hrt-1
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set
to C)
Versions of packages rsync depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libpopt0 1.7-5 lib for parsing cmdline parameters
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue 03 Apr 2007, Francesco Potorti` wrote:
> >have you had a chance to test more recent versions of rsync?
>
> I just tried. The problem does not exist any more. Thank you.
OK, thanks for testing.
Now closing this bug report.
Paul Slootman
--- End Message ---
