On Dec 23, 2005, at 5:37 PM, Paul Slootman wrote:
tags 344592 = sarge
thanks
On Thu 22 Dec 2005, Rick Thomas wrote:
Package: rsync
Version: 2.6.4-6
Severity: normal
Tags: patch
I see no patches...
Perhaps you wanted to tag it as sarge, as testing and unstable have had
2.6.6 since one day after upstream released it.
Sorry... put it down to inexperience. I thought pointing out that it
was fixed upstream was as good as a patch. I guess not.
this bug is fixed in upstream release 2.6.5 (and presumably also in
the
latest upstream release, 2.6.6) from rsync.samba.org
... and from Debian etch.
Cool! Can i just download the .deb from a random etch repository, and
install it on an otherwise all sarge system? As you can tell, I'm a
little bit new to this Debian stuff, though I've been doing Linux (and
UNIX before it) for more years than I want to count.
Quote from the changelog for 2.6.5
- Fixed a case where rsync would erroneously delete some files
and then
re-transfer them when the options --relative (-R) and
--recursive
(-r) were both enabled (along with --delete) and a source path
had a
trailing slash.
This bug makes rsync backups (using e.g. the rsnapshot program) larger
than they need to be.
Does rsnapshot actually use that combination of options?
Dirvish (which I use) isn't affected AFAIK.
Yes. The reason I noticed it was because rsnapshot was doing it. Off
Topic: What made you choose dirvish over rsnapshot?
I'll leave this bug as-is until a new stable version of Debian is
released; there's no way of getting a fix for something like this into
a
point release.
OK. It's sad that the release procedures aren't flexible enough to get
an obvious bug fix like this slipstreamed in, but I understand the
reasons.
Paul Slootman
Thanks! for the quick reply.
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
