similar to: [Bug 1479] --compare-dest suppresses output file if same timestamp present

https://bugzilla.samba.org/show_bug.cgi?id=1479 Summary: --compare-dest suppresses output file if same timestamp present Product: rsync Version: 2.5.7 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=1479 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Summary|--compare-dest suppresses |request the addition of a --

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

https://bugzilla.samba.org/show_bug.cgi?id=9657 Summary: --compare-dest results inconsistent between major 2 and major 3 Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=5647 Summary: A way to make earlier --compare-dest dirs hide later ones Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, I've been attempting to use --compare-dest DIR SOURCE/ DEST/ If a file exists in DEST but is different to the corresponding file in DIR, then the file is updated in DEST. This is what I would expect. I have found that files which do not exist in DEST but do exist in DIR and SOURCE, are not created. Simply touching the file in DEST causes it to be updated. This behaviour seems

https://bugzilla.samba.org/show_bug.cgi?id=4961 Summary: rsync ignores --compare-dest flag? Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: jae@platinumpsi.com

https://bugzilla.samba.org/show_bug.cgi?id=7664 Summary: --compare-dest hangs Product: rsync Version: 3.0.7 Platform: Other OS/Version: Windows NT Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: francois at synways.com

https://bugzilla.samba.org/show_bug.cgi?id=7663 Summary: --compare-dest hangs Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: francois at synways.com QAContact:

I am working with rsync on Debian, package version 3.0.9-1. I am trying to use rsync --compare-dest to make a delta-copy of a directory. In my case, the mtimes are all unreliable. The data is the same, but the times are all messed up and always will be. I am trying to use --compare-dest with --checksum or --size-only and it does not work. All files are transferred and the delta copy

Hi all, I have just migrated my tooling from version 2.6.9 to 3.0.0. Unfortunately my script generated an error message during the execution. Because this command was working perfectly in the previous version I suspect this could be a bug. This is the command that I am executing: rsync -av --link-dest=20080313/ --compare-dest=/data/20080313/ 20080313/ /data/20080314/ It just

https://bugzilla.samba.org/show_bug.cgi?id=13656 Bug ID: 13656 Summary: --link-dest target with symbolic links from different user produces unnecessary error Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component:

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

On Mon, Jun 23, 2003 at 11:12:03PM -0400, Stephen Gildea wrote: > I have a suggestion for how to make the documentation of rsync's > "--compare-dest" option clearer. > > Maybe it would be clearer if I had some problem this option would solve, > but as it is, I couldn't figure it out from the manual. The description > in the rsync 2.5.6 manual page starts:

I must be seriously misunderstanding the man page coverage of --compre-dest. My take was that if a file in compare-dest=dir matches a file in SOURCE/ then it won't be transferred to DEST/. I tried this test. (d1 has single files and 2 subdir with files) cp -a d1 d1a mkdir d2 rsync -avv --compare-dest="./d1a" d1/ d2/ d1a is carbon copy of d1 but still every last file in

Hey. Can anybody spot my mistake? mkdir a b c echo foo > a/test echo foo > b/test rsync -av --compare-dest=b a/ c/ Expected results: no copy of a/test to c/test, since it is already present in b. Actual results: a/test gets copied to c/test What is wrong here? My expectation? my syntax? I'm having the same trouble with --link-dest, and --copy-dest. The behaviour I'm seeing

Hi all. I have just finished a small patch that adds support for multiple --compare-dest or --link-dest args. Its primary usage is to do incremental backups on top of eachother. (My current backup system stores each incremental as a single diff of the latest full.) Example: First full backup: rsync -a somedir full-20040415/ First incremental: rsync -a --compare-dest=../full-20040415 \

Hi all. A while ago (April 15th or so) I posted a patch that allows rsync to take multiple --compare-dest or --link-dest arguments, allowing fetching of files not present in multiple trees. I never got any feedback on it, though, so I'm picking it up again. :) Is there any interest in such a patch at all? Below is the usage example i outlined back then; --start-- [...] Its primary usage is

When I'm running "rsync --compare-dest" on a local Linux volume (ext4) it works as expected (duplicate files not created) however when same commands with same options are run on NTFS USB drive (in my scenario below mounted to /share/external/sdt5) all the files are copied regardless if they have been updated or not. I have spent many hours trying to figure out what could be wrong and

On Tue, 2008-08-12 at 19:11 +0800, Thomas Gutzler wrote: > I've recently noticed that running rsync -m --compare-dest creates > empty directories, even though it should be prevented by the -m flag. > Try rsync -avm --compare-dest=/path/to/dir/ /path/to/dir/ foo > and you get a nice copy of the directory structure in foo - with no files in it. > I was wondering if there's a