rsync problems from flist.c change

Wayne Davison wayned at
Thu Apr 22 09:45:15 GMT 2004

On Thu, Apr 22, 2004 at 08:21:24AM +0200, Kurt Hornik wrote:
> I can partially reproduce this by (starting from a state where the two
> dirs are in sync) copying an additional file into 'Recommended' and
> trying different versions of rsync to see whether the file gets
> removed.

Does the file you added match one of the excluded files (including any
default cvs-exclude patterns and patterns read from $HOME/.cvsignore or
taken from the $CVSIGNORE environment variable, but ignoring the
individual .cvsignore files, which you are excluding)?  You can add an
extra level of -v to see all the files that are being excluded from both
created lists (the sender's list and the receiver's deletion-comparison

If you don't see the additional file you created being excluded, you can
add yet another -v level to see all the make_file() calls.  You should
see the extra file on the receiving side either mentioned in a
make_file() call or in an "excluding" message.  If the file goes into
the receiving side's list, is not present in the sending-side's list,
and the file is not deleted, then there's some kind of a bug.

Let me know what you find out.


More information about the rsync mailing list