> I got 3.1 to build all right on OS X but it won't run without stalling and
> lots of errors. Is it working for you or anyone else yet or have the problems
> come to light?
Yes, now I'm using it in anger I'm seeing several fatal errors like the
following (I'm syncing with a local mount point,
> However, attempting to build the new 3.1.0 release on a brand new Mountain
> Lion box with my standard 'fileflags' and 'crtimes' patches applied, make
> fails, reporting that 'force_change' is undeclared.
Scott Lasley suggested a workaround for this: apply the 'hfs-compression' patch
in addit
Returning to this list after a long hiatus: rsync 3 has been working very well
for me for many years, as a supplementary backup tool for MacOSX.
However, attempting to build the new 3.1.0 release on a brand new Mountain Lion
box with my standard 'fileflags' and 'crimes' patches applied, make fai
The -d option was added in 2.6.4, almost exactly 3 years ago. There
seems to be a significant amount of 2.6.3 still around (which is 3.5
years old), which is a little sad to see, but I suppose not that
unexpected.
Rsync 2.6.3 is the default on OS X 10.5 Leopard, released in October
last
I think you hit the nail on the head. I put the crtimes.diff first
because I was simply swapping it in for osx-create-time.diff in
Axel's email "3.0.0 test failure MacOS X 10.4.11".
Upon invoking make, this error in the ordering of the patches, on my
part yielded:
Check the output of your
I did a lot of tests on Tiger and Leopard with this good patch and
it seems it doesn't need the --force-change options.The bbouncer
test comes up clean with or without it. Is that true? Or should we
use those option just in case? Should we have the option? Rob
My guess is you don't need --f
I am running MacOS X 10.4.11 on PPC. The following is a synopsis of
my installation procedure (as gathered from the various emails in
the archive) - note that I had trouble with crtimes.diff and went
back to osx-create-time.diff. Please let me know if I have included
anything spurious or mi
Hi All,
I just tried (on OS10.5.2) the new fileflags.diff patch
patch -p1 patch -p1 rej's )
then
./configure
make
then tried it out but it isn't copying the creation dates now
I noticed there's a new nightly build - if I patch against that, I
only see the first of the rejects:
amorton$
On Sat, Feb 23, 2008 at 10:41:24PM -0500, Matt McCutchen wrote:
flags.diff still exists. Is that intentional?
Yeah, it was briefly still available until I had time to change the
crtimes patch to depend on fileflags.diff instead of flags.diff.
That is now done, so the flags.diff patch is g
The resulting patch is now called fileflags.diff (to match the
option name):
http://rsync.samba.org/ftp/rsync/patches/fileflags.diff
It looks like there's a need to modify the crtimes patch
consequentially:
patch -p1 Incidentally, I haven't noticed any endian issues when copying from
In
I've just released rsync 3.0.0pre9. We needed one last bug-fix
release prior to the 3.0.0 final release, so here it is. I'm not
anticipating any large changes prior to that milestone. Please help
to test it to ensure that we're ready to go! Send email to the
rsync mailing list with your
That's the missing info I needed to fix the problem. There was a
call in the sender that was being run when it shouldn't have in dry-
run mode. The latest dev version (git, nightly, etc.) has this fixed.
And it looks like all the problems I was having are now resolved.
Many thanks to all!
My latest version of the crtimes.diff patch is now based on having
the flags.diff patch applied first, so they'll work together now.
You'll need to have the latest dev version of the source and the
patches, though (see the downloads page for the various ways to
access the source).
Incide
I have a similar problem. I'm trying to specify a custom per-
directory filter using
--filter='dir-merge .rsync-filter-m'
but because the whole thing is double-quoted the filter rule
arrives in single quotes. I can't simply leave out the quotes here
because the --filter option onl
The shell does not strip the single quotes because they are inside
double quotes. Thus, rsync is getting filter patterns containing
single quotes, which would obviously prevent the filters from
matching.
You can just remove the single quotes, but then the shell will try
to expand the wildca
15 matches
Mail list logo
