similar to: Rsync 3.0.0pre9 released

Displaying 20 results from an estimated 10000 matches similar to: "Rsync 3.0.0pre9 released"

2009 Apr 18
8
DO NOT REPLY [Bug 6276] New: crtimes.patch does not preserve creation dates on Mac x86_64 only
https://bugzilla.samba.org/show_bug.cgi?id=6276 Summary: crtimes.patch does not preserve creation dates on Mac x86_64 only Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2008 Feb 26
2
fileflags.diff patch
Hi All, I just tried (on OS10.5.2) the new fileflags.diff patch patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff (see result below- I fixed the rej's ) then ./configure make then tried it out but it isn't copying the creation dates now.... just wondering if I missed something .. Rob D robert-dutoits-powerbook-g4-15:rsync-3.0.0pre10 astrid$ patch -p1
2008 Mar 03
1
Passed all tests with flying colors on Mac OS X 10.4.11 - synopsis of installation and testing
Awesome work Wayne. I have been following the various threads about running rsync 3.0.0 on MacOS X 10.4.11 and wanted to confirm that following all the various bits of advice yields a clean running rsync (as tested by backup bouncer). 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
2008 Feb 19
1
broken pipe
Hi All, I have a client and we are trying to create a backup for several folders on OSX 10.4.11 with rsync 3.0.0pre9. One folder copies fine but the other three generate this error and I am stumped. using: rsync -aHAX --fileflags --crtimes -v we get; sending incremental file list rsync: writefd_unbuffered failed to write 82 bytes [generator]: Broken pipe (32) rsync error: error in
2016 Nov 23
5
[Bug 12440] New: make "rsync -N" == "rsync --numeric-ids" ?
https://bugzilla.samba.org/show_bug.cgi?id=12440 Bug ID: 12440 Summary: make "rsync -N" == "rsync --numeric-ids" ? Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at
2018 Jul 11
5
[Bug 13522] New: Patch fileflags.diff and crtimes.diff
https://bugzilla.samba.org/show_bug.cgi?id=13522 Bug ID: 13522 Summary: Patch fileflags.diff and crtimes.diff Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:
2008 Mar 02
1
3.0.0 test failure MacOS X 10.4.11
Hello all, I was eager to test the fresh release with MacOS X using "bbouncer" This is how I compiled and run the tests: patch -p1 <patches/osx-create-time.diff patch -p1 <patches/fileflags.diff ./prepare-source patch -p1 <patches/backup-dir-dels.diff ./configure make make test sudo make install Then compiling and running "bbouncer" from
2020 Aug 11
4
[Bug 14463] New: rsync 3.2.2 server protocol error
https://bugzilla.samba.org/show_bug.cgi?id=14463 Bug ID: 14463 Summary: rsync 3.2.2 server protocol error Product: rsync Version: 3.2.0 Hardware: All OS: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne at opencoder.net Reporter:
2002 Jul 17
3
Case Sensitive Problem
I am using samba to share a directory that lives on an OpenBSD 3.1 box. The client is my linux box. I want to mount this directory so I can use my own tools on the linux box to edit the code. My problem is that there is a file "boucer" which is an executable and a "Bouncer" directory. I'm sure you can see my problem. I tried putting case sensitive = yes in the
2008 Jul 04
3
Rsync "roadmap" and version numbering (3.1.0 vs 3.0.4)
I think it's about time to start adding some new features to rsync 3 instead of just making bug fixes, so I'm planning to starting work on version 3.1.0. This will start the use of a new version numbering idiom where feature releases increment the sub-version number, while patch releases continue to increment the sub-sub-version number. I'm not using an odd/even scheme for
2008 Feb 15
4
Revised flags patch
Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the
2008 Feb 26
4
rsync-3.0.0pre10 and iconv
Hello, I am trying to get rsync-3.0.0pre10 --iconv option working between two linux hosts in local network. The client host is running Fedora Core 4 (kernel 2.6.17) and is using iso8859-1 character set. LANG=en_US The daemon host is running Centos 5 (kernel 2.6.18) and is using utf-8 character set. LANG=en_US.UTF-8 Rsync is transferring files properly without --iconv switch: fc4: (connected
2008 Apr 08
1
Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)
I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the
2008 Apr 08
1
Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)
I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the
2009 Jan 21
3
Rsync with OS X 10.3
Hi Jason, Here's rsync10.3xattr_supportv0.6.diff. You can find fileflags.diff and crtimes.diff (that are not from me, but I strongly recommend you to install) here: http://samba.anu.edu.au/ftp/rsync/src/rsync-patches-3.0.5.tar.gz As you could see in the mail from the mail-list, this version have a bug with filenames containing slashes ("/"). They are converted to colons
2007 Dec 02
3
creation date and OSX
Hi, I've been using rsync (OSX Tiger now Leopard) to backup my home folder daily using -a -H -A -X link-dest=dir to make incremental backups. There was a problem though since many files especially images, movies etc would be recopied each time instead of creating hard links. I have been testing the pre5 release and found that it seems to make hard links correctly for all files. I
2011 Nov 02
12
[Bug 8566] New: Spotlight comments (extended attributes) are not synced
https://bugzilla.samba.org/show_bug.cgi?id=8566 Summary: Spotlight comments (extended attributes) are not synced Product: rsync Version: 3.0.9 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org
2008 Jan 24
9
Making rsync compile under Mac OS X 10.3.9 with extended attributes
Somebody knows if it's possible to compile rsync (version 3 would be great, but can be 2.6.x) under Mac OS X 10.3.9 with extended attributes? Under OS 10.3.9 the Apple shipped rsync have not yet the -E argument option. RsyncX have a double free bug that is annoying. "Q" rsync 2.6.6 with extended attributes binary only works on 10.4 and above. I have tried to compile rsync
2007 Oct 07
2
DO NOT REPLY [Bug 5012] New: iconv: client charset used by server process
https://bugzilla.samba.org/show_bug.cgi?id=5012 Summary: iconv: client charset used by server process Product: rsync Version: 3.0.0 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: kaarle@web.de
2008 Sep 27
1
Bug with crtimes and hard links?
I've been getting spurious unnecessary copying of files on OSX when using the crtimes patch and the --crtimes -H options (version 3.0.4). I can reliably demonstrate it (on OSX 10.5) by doing this several times (as root): rsync -v -N -axHAX --delete-during --fileflags --force-change /usr/ bin/ /tmp/foo/ I think I've tracked it down to the hard-link processing code in