similar to: [Bug 2780] New: fix acl patch

Skipped content of type multipart/alternative-------------- next part -------------- # ./configure configure.sh: Configuring rsync 3.0.1 checking build system type... hppa2.0w-hp-hpux11.11 checking host system type... hppa2.0w-hp-hpux11.11 checking target system type... hppa2.0w-hp-hpux11.11 checking for gcc... no checking for cc... cc checking for C compiler default output file name... a.out

I'm trying to get an old FreeBSD 4.11 server to talk to a newer FreeBSD 7 server that is running rsync 3.0.4 but I am running into an error with extended file attributes: Basic steps: Applied the fileflags patch per the instructions: patch -p1 <patches/fileflags.diff ./prepare-source Ran the following configure line: ./configure --with-included-popt --disable-iconv

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

I am an rsync newbie trying to setup rsync on a HP UX 11.0 server, but am running into problems in my "make". I am using gcc version 3.3.2 and rsync-2.6.6.tar.gz. Would any of you have ideas on troubleshooting this issue? I haven't had much luck googling info on this, with the exception of switching from HP's simple c compiler to gcc. The warnings and errors I am recieving

Unfortunately I don't know how to write AC macros to properly solve this problem but Cygwin does not (any longer) include cygwin/acl.h from sys/acls.h which is required for Solaris ACL data structures to work. So the CASE statement improperly short-circuits the logic. I have confirmed that Rsync builds using POSIX ACLs but haven't tested said functionality. diff --git a/configure.ac

https://bugzilla.samba.org/show_bug.cgi?id=7489 Summary: rsyncd segfaults using daemon exclude filter Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: michael.roberts at hp.com

Applying the xattr and acl patch to 2.6.9, running ./prepare-source and config with ./configure --enable-xattr-support results in a version which fails to transfer with the error msg 'wrong write used in receiver' and complaints about protocol mismatch. I see there's a patch for a similar problem when SUPPORT_ACLS is defined; anybody done one for --xattrs? No, I'm not

Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear:

I was pretty amased to even get this game to install, but I did. And I can even play a skirmish game. But the campaing mode just doesn't want to co-operate. After loading for a while it just crashes. Here is the log (... meens that the previouse line was repeated multiple times): fixme:win:EnumDisplayDevicesW ((null),0,0x1d2ecb0,0x00000000), stub! fixme:win:EnumDisplayDevicesW

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> This is a huge all-in-one patch and deserves a little cleanup and splitting. However, I wanted to get it out here for some feedback. My primar motivation to use SHA1 for checksumming (by default) instead of MD5 is not the additional security bits but performance. On a decent x86 box the SHA1 performance is almost the same as

https://bugzilla.samba.org/show_bug.cgi?id=5565 Summary: xattrs not set on locked files that already exist on target Product: rsync Version: 3.0.3 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

In the mandriva rpm of rsync, we apply for our rpm the acl patch in the patches directory. I am trying to update our rpm to rsync 2.6.6 but one of the test failed with this patch. It seems to be a minor problem, but can you have a look ? Thanks by advance. Following the message (a bit long): ----- itemize log follows Testing for symlinks using 'test -h' +

I got numerous warnings when building rsync on IA64 (Itanium-2) using Intel C/C++ compiler (see attached). Is this expected? Thanks, Michael -------------- next part -------------- Script started on Fri 21 Sep 2007 06:14:05 PM BST ~/src$ ls -alt total 222884 -rw-r--r-- 1 mccssmb2 mcc101 0 Sep 21 18:14 build_rsync drwxr-xr-x 8 mccssmb2 mcc101 4096 Sep 21 18:14 . -rw-r--r-- 1

Hi, I'm using 2.6.9 but I get: recv_files phase=1 generate_files phase=2 recv_files phase=2 recv_files finished generate_files phase=3 deleting in home delete_in_dir(home) [generator] make_file(home/administ,*,2) Internal error: wrong write used in receiver. _exit_cleanup(code=2, file=io.c, line=1204): entered _exit_cleanup(code=19, file=main.c, line=1182): entered rsync error: received

https://bugzilla.samba.org/show_bug.cgi?id=14076 Bug ID: 14076 Summary: 3.13 - lib/sysacls.h:118:13: error: array type has incomplete element type 'struct acl' Product: rsync Version: 3.1.3 Hardware: x64 OS: All Status: NEW Severity: normal Priority: P5

https://bugzilla.samba.org/show_bug.cgi?id=3029 Summary: rsync 2.6.6 with acl patch compile fails Product: rsync Version: 2.6.5 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just attempted to build 3.0.23pre1 on HP-UX 11.11 today, preparing for a planned move to a later version of 3.0.x (we're currently down at 3.0.11). Configure ran fine, but make eventually failed here: Compiling lib/sysacls.c cc: warning 422: Unknown option "fPIE" ignored. cc: "lib/sysacls.c", line 1277: warning 611: Type

This is an updated version of my patches to get rsync to build and run its tests on the Stratus VOS operating system. I have updated this patch to apply cleanly to the current copy of HEAD. I also ran the test suite and discovered that I needed to tweak a few spots in the Makefile to append the executable suffix (VOS is one of the few systems that has a required executable suffix). There are a

This is a corrected version of the patch I originally submitted on September 5th, and resubmitted on October 14th. I have removed the changes that added $(CFLAGS) to the link-only invocations of gcc. Otherwise, the patch is the same as before. My thanks to Paul (prj@po.cwru.edu) for noticing my error and kindly correcting me. ** text of original letter, with corrections ** I had to make some

I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile. Most other packages (e.g. Samba) seem to allow CPPFLAGS to be set by the user. Since this is how I