* "rsync.project via rsync"
:
Wrote on Wed, 15 Jan 2025 09:34:10 +1100:
> sorry about the prefix changes in rsync-patches. We're going to be dropping
> the whole rsync-patches system soon anyway, as it really isn't working
> well. It was supposed to be a staging ar
Hi,
This is mostly intended for the maintainers to read.
What's intended way to actually get patches merged into rsync?
I've tried:
- Mailing list posts
- GitHub PRs
--ignore-non-existing-directory
https://lists.samba.org/archive/rsync/2015-November/030455.html
https://github.com/Rs
Hi,
Is there any information anywhere about what specifically is broken with
the macOS-specific patch:
rsync-3.1.3/patches/hfs-compression.diff
It has been broken since rsync 3.1.3.
I searched Google and https://bugzilla.samba.org/ but couldn't find any
information regarding what is b
Yet another broken link "patches dir" [1] on the rsync bug-tracking page [2].
[1] https://download.samba.org/pub/rsync/dev/patches/
[2] https://rsync.samba.org/bugzilla.html
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change opti
On Fri, Oct 25, 2013 at 6:38 AM, Vitezslav Cizek wrote:
> rsync-patches/slp.diff is still using lp_numserv which was removed by
> commit b583594ac7d2f8a38aca85c1bfa4b1487122377a
>
Thanks for pointing that out. I'm fixing that in the git repo.
..wayne..
--
Please use repl
Hello,
rsync-patches/slp.diff is still using lp_numserv which was removed by
commit b583594ac7d2f8a38aca85c1bfa4b1487122377a
Signed-off-by: Vitezslav Cizek
---
slp.diff | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/slp.diff b/slp.diff
index a9703f1..953b400 100644
--- a
Dear collegaues,
please evaluate the patch attached, which allow to use both --detect-renamed
and --fileflags extra features.
This is meta-patch which sould be applied to detect-renamed. fileflags patch
should be applied first, following by the modified detect-renamed patch.
It is included in
Sorry for the multiple posts, am thinking about this problem
in between working on other stuff... and stuff comes up.
But bottom line -- I would look at the source of coreutils "dd" program
and find out how they do direct I/O. I know they had to deal with
alignment issues when the Linux kernel b
In thinking about this some more, you probably
want to limit your O_DIRECT to just opens on files --
not sockets.
I think that might be the cause of the error I got.
The other stuff may still apply, but may be OS dependent.
It doesn't look like it is real easy to tell in the
open routine where
On Mon, 18 Feb 2013, Linda Walsh wrote:
Hi dag, I really appreciate your working on this,
but it is really annoying hard and tedious.
_I_ am not certain about all the requirements of Direct I/O,
I.e. would have to research (goog/kernel source...etc).
It may be different on different platforms
that I applied your patch to was from the openSuSE
12.1 source rpms. Drop-cache is one of the patches they include, I'd
forgotten about it...There's a bunch .. I don't know if a bunch of patchs
ship with the original source to be used as wanted...they looked like a
something separate.
On Sat, 16 Feb 2013, Linda Walsh wrote:
I wondered about that as well -- could speed things
up by 30% over going through the slow linux buffers.
One thing that the 'dd' people found out though was
that if you do direct I/O, memory and your I/O really
do have to line up -- it may be that only 51
s quite trivial, I patched
> > both v3.0.9 and master branch and included the patches here.
>
> When I drop the 3.0.9 diff into my otherwise working spec file for 3.0.9
> on opensuse build service, it patches and builds with no error, but
> "make test" fails:
At
Dag Wieers wrote:
Hi,
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the patches here.
Sigh.
It hasn't been done because it
patches here.
When I drop the 3.0.9 diff into my otherwise working spec file for
3.0.9 on opensuse build service, it patches and builds with no error,
but "make test" fails:
Attached is an updated patch which takes care of the test cases.
Kind regards,
---
Tried this patch, but
master branch and included the patches here.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
branch and included the patches here.
When I drop the 3.0.9 diff into my otherwise working spec file for
3.0.9 on opensuse build service, it patches and builds with no error,
but "make test" fails:
Attached is an updated patch which takes care of the test cases.
Kind regards,
Success!
branch and included the patches here.
When I drop the 3.0.9 diff into my otherwise working spec file for
3.0.9 on opensuse build service, it patches and builds with no error,
but "make test" fails:
Attached is an updated patch which takes care of the test cases.
Kind regards,
Awes
On Thu, 14 Feb 2013, Brian K. White wrote:
On 2/14/2013 9:50 AM, Dag Wieers wrote:
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the patches here.
When
On 2/14/2013 9:50 AM, Dag Wieers wrote:
Hi,
Since a --direct-io feature was requested a few times the past decade
with little response and the actual patch is quite trivial, I patched
both v3.0.9 and master branch and included the patches here.
If this functionality is acceptable I don't
Hi,
Since a --direct-io feature was requested a few times the past decade with
little response and the actual patch is quite trivial, I patched both
v3.0.9 and master branch and included the patches here.
If this functionality is acceptable I don't mind spending the additional
effo
Hello,
i have found, that major distros (especially opensuse) ship their rsync
packages with a lot of patches which i don`t find in the official rsync-patches
git.
Maybe there is a reason for that or i missed something or looked wrong, but
for convenience/transparency i have compiled a list
Hi Tony,
> fileflags and crtimes and hfs-compression patches applied
That should do it. It comes up perfect for me on the Bbouncer tests with those
three patches. Mike will speak for himself, but He has done some tweaking with
other patches he made to customize the build for Carbon Copy Clo
, btw, with the fileflags and crtimes
and hfs-compression patches applied; I just wondered if the others that he
mentioned are needed.
http://www.bombich.com/rsync.html
This is a very useful site that Mr. B. has maintained for several years --
thanks!
--
Tony Reed
anthony.r...@gmail.com
--
Pleas
On Thu, May 28, 2009 at 09:04:59PM -0400, Matt McCutchen wrote:
> How can I access the rsync maintained patches repository with the git
> tools?
Sorry for forgetting to get that taken care of. The issue turned out to
be that the samba site defaults to not allowing "git:"
On Fri, 2009-05-29 at 10:34 +0200, Petr Uzel wrote:
> On Thu, May 28, 2009 at 09:04:59PM -0400, Matt McCutchen wrote:
> > Wayne,
> >
> > How can I access the rsync maintained patches repository with the git
> > tools?
> See
> http://www.mail-archive.com/rsync@l
On Fri, 2009-05-29 at 10:46 +0200, Paul Slootman wrote:
> On Thu 28 May 2009, Matt McCutchen wrote:
> >
> > $ firefox http://gitweb.samba.org/?p=rsync.git;a=summary
>
> I guess you left out the quotes you must have used here,
> as otherwise a=summary won't be included in the url...
Yes, I sort o
On Thu 28 May 2009, Matt McCutchen wrote:
>
> $ firefox http://gitweb.samba.org/?p=rsync.git;a=summary
I guess you left out the quotes you must have used here,
as otherwise a=summary won't be included in the url...
Paul
--
Please use reply-all for most replies to avoid omitting the mailing lis
On Thu, May 28, 2009 at 09:04:59PM -0400, Matt McCutchen wrote:
> Wayne,
>
> How can I access the rsync maintained patches repository with the git
> tools? These work:
>
> $ firefox http://gitweb.samba.org/?p=rsync.git;a=summary
> $ git clone git://git.samba.org/rsync
Wayne,
How can I access the rsync maintained patches repository with the git
tools? These work:
$ firefox http://gitweb.samba.org/?p=rsync.git;a=summary
$ git clone git://git.samba.org/rsync.git
$ firefox http://gitweb.samba.org/?p=rsync.git/patches.git;a=summary
So I thought this might work
sing -u with diff makes for better patches. Thanks for your
feedback!
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
These two small changes enable 3.0.6 to compile and link on AIX 3.2:
diff -r rsync-3.0.6/lib/getaddrinfo.c rsync-3.0.6-new/lib/getaddrinfo.c
298c298
< if (!inet_aton(node, &ip)) {
---
> if (!inet_pton(AF_INET, node, &ip)) {
diff -r rsync-3.0.6/lib/sysac
On Fri, 2009-03-13 at 16:44 -0700, Wayne Davison wrote:
> On Fri, Mar 13, 2009 at 06:57:15PM -0400, Matt McCutchen wrote:
> > I would have thought it more natural to have branches "patches-master"
> > and "patches-3.0.x" in the main repository. Is there
Le 19 janv. 09 à 21:53, tim lindner a écrit :
Thanks for this. Everything has been working fine. I did encounter
one problem. It didn't like it when colons were in filenames. Rsync
would spit out an error and move to the next file.
I remember (sorry I don't have a reference) that HFS disal
Check that ACL's are enabled on the destination volume.
Details on how to do this are available from the following URL :
http://connect.homeunix.com/lbackup/doku.php?id=access_control_lists
Hope this helps.
I am using rsync 3.0.3 to copy a remote RAID volume on one Xserve to
the
local RAID vo
I am using rsync 3.0.3 to copy a remote RAID volume on one Xserve to the
local RAID volume on an other Xserve. Both Xserves are running OS X Server
10.4.11.
I have compiled rsync 3.0.3 on both machines and patched it following Mike
Bombich's instructions at http://www.bombich.com/mactips/rsync.html
On Tue, Apr 15, 2008 at 02:06:28AM +0200, Ruediger Oertel wrote:
> patches/xattrs.diff repeats the man-page change from patches/slp.diff
> producing an error if you try to apply both patches.
I'm looking into why the change to rsyncd.conf.yo made in the slp patch
got added to all the p
HI,
patches/xattrs.diff repeats the man-page change from patches/slp.diff
producing an error if you try to apply both patches.
--
with kind regards (mit freundlichem Grinsen),
Ruediger Oertel ([EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED
On Wed, 2008-02-06 at 17:36 +0100, Frank Purmann wrote:
> Your patch should solve my problem but I can not download the patch.
>
> http://cvs.samba.org/cgi-bin/cvsweb/~checkout~/rsync/patches/transliterate.diff?rev=1.1&content-type=text/plain
> gives me an error.
For some rea
On Sat, Feb 02, 2008 at 04:11:03PM -0500, Simo Sorce wrote:
> xattrs.diff contains the same change to proto.h that acls.diff contain making
> patch fail if you apply both (as suggested in xattrs.diff header).
I've fixed the support/patch-update script so that it properly diffs the
generated files
On Sat, 2008-02-02 at 22:31 +0100, Vitorio Machado wrote:
> How did you proceed to patch?
>
> Here:
> iMac:~ lag$ mv /Users/lag/Desktop/rsync-3.0.0pre8\ 2/patches/ /Users/
> lag/Desktop/rsync-3.0.0pre8/
> iMac:~ lag$ cd Desktop/rsync-3.0.0pre8
> iMac:~/Desktop/rsync-3.0
How did you proceed to patch?
Here:
iMac:~ lag$ mv /Users/lag/Desktop/rsync-3.0.0pre8\ 2/patches/ /Users/
lag/Desktop/rsync-3.0.0pre8/
iMac:~ lag$ cd Desktop/rsync-3.0.0pre8
iMac:~/Desktop/rsync-3.0.0pre8 lag$ patch -p1 And it goes fine... As you said both acl and xattr try to patch
proto
On Sat, 2008-02-02 at 15:41 -0500, Simo Sorce wrote:
> On Sat, 2008-02-02 at 18:49 +0100, Vitorio Machado wrote:
> > It's in separate here http://samba.anu.edu.au/ftp/rsync/rsync-
> > patches-3.0.0pre8.tar.gz
>
> Oh, thanks, haven't notice any message on the l
On Sat, 2008-02-02 at 18:49 +0100, Vitorio Machado wrote:
> It's in separate here http://samba.anu.edu.au/ftp/rsync/rsync-
> patches-3.0.0pre8.tar.gz
Oh, thanks, haven't notice any message on the list telling the packages
were separated, sorry for the noise.
Simo.
--
Simo Sorc
It's in separate here http://samba.anu.edu.au/ftp/rsync/rsync-
patches-3.0.0pre8.tar.gz
Le 2 févr. 08 à 18:19, Simo Sorce a écrit :
What happened to the patches dir?
It is missing in the pre8 tarball.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
--
To unsubscribe or change options:
What happened to the patches dir?
It is missing in the pre8 tarball.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On 9/2/07, Wayne Davison <[EMAIL PROTECTED]> committed:
> A slightly changed version of Matt's %C (checksum) logging patch.
Cool! However, I'm not sure you need the special check to change a
checksum that is genuinely all zeros to all ones. The risk of rsync
ignoring a read error because the che
On 7/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I understand that it's a fairly low probability, and
depends on some questionable configurations, but rsync is well-known
to be both reliable and deterministic. I'd hate for something like
this to start chipping away at that reputation, eve
Date: Mon, 2 Jul 2007 21:18:57 -0400
From: "Matt McCutchen" <[EMAIL PROTECTED]>
The technique Wayne and I are discussing assumes only that the clock
on *each side* never steps backwards.
Um, and note, btw, that the pathological FSB-spread-spectrum/NTP
interaction I mentioned in my
Date: Mon, 2 Jul 2007 21:18:57 -0400
From: "Matt McCutchen" <[EMAIL PROTECTED]>
The technique Wayne and I are discussing assumes only that the clock
on *each side* never steps backwards. It compares the current mtime
and ctime on each side to the previous mtime and ctime on th
On 7/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Unreliable. If you sync up at the beginning of a run, and then the
remote system executes a large clock step (e.g., because it's not
running NTP or it's misconfigured, or it is but NTP has bailed due to
excessive drift from hardware issues
Date: Mon, 2 Jul 2007 08:43:39 -0400
From: "Matt McCutchen" <[EMAIL PROTECTED]>
> *Note that "now" for a particular disk may not be the same as time() if
> the disk is remote, so network filesystems can be rather complicated.
That's easy to fix: get your "now" by touching a fi
On 7/2/07, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Mon, Jul 02, 2007 at 08:43:39AM -0400, Matt McCutchen wrote:
> What do you mean? There's no way to fix the example I gave with
> xattrs
Not so. I went on to explain how that is possible in my prior email
(i.e. avoiding caching a checksum o
On Mon, Jul 02, 2007 at 10:28:25AM -0700, Wayne Davison wrote:
> It is if you're doing one check to see if a file is being updated (e.g.
> stat() followed by time() to compute "now"). If time rolls over between
> the two calls, you may have just missed that the mtime would now match
> if you did a
On Mon, Jul 02, 2007 at 08:43:39AM -0400, Matt McCutchen wrote:
> What do you mean? There's no way to fix the example I gave with
> xattrs
Not so. I went on to explain how that is possible in my prior email
(i.e. avoiding caching a checksum on a "now" mtime file is all that is
needed).
> That's
On 7/1/07, Wayne Davison <[EMAIL PROTECTED]> wrote:
[...] It is still useful for allowing a server to cache the
checksum values without requiring any extra files. As long as it is
used on files that aren't being actively updated, it works great.
OK, that's reasonable.
> Second, it is imposs
On Sat, Jun 30, 2007 at 04:17:29PM -0400, Matt McCutchen wrote:
> First, setting the xattr hits the file's ctime.
Yeah, I realize that, and that's why none of the xattr values cache the
ctime. This does mean that this method isn't good for updating checksum
values on existing files (since a gener
Matt McCutchen wrote:
> Second, it is impossible to make xattr-based checksum caching
> foolproof against same-second modification. Suppose a file is written
> during second 5 and then rsync caches its checksum during second 8;
> now the file has mtime 5 and ctime 8. Sometime later, rsync notices
On 6/30/07, Wayne Davison <[EMAIL PROTECTED]> committed:
Added Files:
checksum-xattr.diff
Log Message:
A simple patch that lets rsync use cached checksum values stored in
each file's extended attributes. A perl script is provided to create
and update the values.
Wayne,
You should be a
Hello,
As soon as I find a little time I will try to manually apply Apple's
extended attributes patches (that apply to the 2.6.3 version) to the
trunk rsync 3. I say manually as I already noticed some differences
that would make a patch impossible.
There is a clash with the -E option
On Thu, Feb 09, 2006 at 06:11:01PM -0500, Matt McCutchen wrote:
> However, the ACL patch tried to patch autom4te.cache files
Oops! That was a weird side-effect of my adding extra features to my
release script (which now makes use of the improved verify-patches
script). Thanks for pointing t
I'm trying out rsync 2.6.7pre1. Since the distributed patches now patch
generated files, I thought I could simply extract, apply the ACL patch,
configure, and make. However, the ACL patch tried to patch
autom4te.cache files I didn't have because I didn't autoconf myself.
I'm
On Fri, Aug 26, 2005 at 04:56:35PM -0700, Steve Dekorte wrote:
> Doesn't that require a cvs server?
On your part? No. Just check out the files to your local disk.
..wayne..
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb
On Aug 26, 2005, at 4:56 PM, Steve Dekorte wrote:
Doesn't that require a cvs server? My goal here is not to use a scm
that requires anything but me occasionally copying my files to the
rsync repo.
correction:
My goal here is not to use a scm that requires me to do anything but
occasionally c
On Aug 26, 2005, at 4:30 PM, Wayne Davison wrote:
On Wed, Aug 24, 2005 at 03:25:37PM -0700, Steve Dekorte wrote:
- checkout an rsync repo
- make some changes to my copy
- build a patch by diffing my copy and the copy on the rsync server
over rsync
That's easy with standard cvs commands. See
On Wed, Aug 24, 2005 at 03:25:37PM -0700, Steve Dekorte wrote:
> - checkout an rsync repo
> - make some changes to my copy
> - build a patch by diffing my copy and the copy on the rsync server
> over rsync
That's easy with standard cvs commands. See the cvs-checkout
instructions on the download
Is there any way to do the following?:
- checkout an rsync repo
- make some changes to my copy
- build a patch by diffing my copy and the copy on the rsync server
over rsync
-- Steve
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: htt
On Wed, Jan 26, 2005 12:18 PM, Chris Shoemaker wrote:
> It's doable, but not trivial. It involves a more "complete" dry-run
> implementation. It's probably a nice project for someone getting into
> hacking on rsync. If I had more time for rsync hacking, this is
> probably the functionality I'd
On Wed, Jan 26, 2005 at 10:57:21AM -0600, Dave Whitinger wrote:
> On Wed, Jan 26, 2005 11:50 AM, Chris Shoemaker wrote:
>
> > Look at "batch mode." Except it actually applys changes, too.
>
> Thank you, Chris!
>
> That's excellent that most of the code is already written. All
> that is needed
On Wed, Jan 26, 2005 11:50 AM, Chris Shoemaker wrote:
> Look at "batch mode." Except it actually applys changes, too.
Thank you, Chris!
That's excellent that most of the code is already written. All
that is needed now is something like "dry-run", that will tell it
not to apply the changes, but
On Wed, Jan 26, 2005 at 07:41:36AM -0600, Dave Whitinger wrote:
> I've been using rsync to remotely backup my MySQL databases
> (totalling over 3 gigabytes) and it works nice and fast.
>
> Now I'm trying to setup my system to save yesterday's backup
> before applying today's backup, but it's not r
I've been using rsync to remotely backup my MySQL databases
(totalling over 3 gigabytes) and it works nice and fast.
Now I'm trying to setup my system to save yesterday's backup
before applying today's backup, but it's not really feasible to
keep a 3gig backup for each day, and I'd rather just sto
On Sat, Apr 17, 2004 at 08:45:15PM +0200, John Bowman wrote:
> I tried out the subdir-exclude patch and it works well for me. The
> next release of rlbackup (coming in a few days) will use this version.
Note that I renamed the option in the patch that comes along with the
2.6.1pre-2 release; it i
Hi.
Here's a patch for copying the atimes of files when -t/--times is
given. I bumped the protocol to 29 since it sends more data over the
wire. It obviously does not send the atime if it's sending data to an
older rsync version.
It passes all the tests (including the added atime.test) for me o
my error and
kindly correcting me.
** text of original letter, with corrections **
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
** This is a resend of mail I originally sent on September
5th. I am still interested in getting these patches
applied, and getting a new config.guess and config.sub.
Is there anything else I need to do in order to get
these changes accepted? Thanks. PG
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
adata support for
HFS+ on Darwin... but not the current patches available here, which I'd
like to test.
What can be done to help facilitate integrating these changes to
the main tree? It would be extremely nice to be able to track the main
development transparently, without
On 27 Mar 2002, "Nelson H. F. Beebe" <[EMAIL PROTECTED]> wrote:
> I found that my mail client reported invalid messages in the
> just-downloaded rsync.mbox.
>
> Further examination showed that they are due to instances of
> unprefixed words "From" at beginning of line in the message body.
> Onc
On 27 Mar 2002, "Nelson H. F. Beebe" <[EMAIL PROTECTED]> wrote:
> I found that my mail client reported invalid messages in the
> just-downloaded rsync.mbox.
>
> Further examination showed that they are due to instances of
> unprefixed words "From" at beginning of line in the message body.
> Onc
I found that my mail client reported invalid messages in the
just-downloaded rsync.mbox.
Further examination showed that they are due to instances of
unprefixed words "From" at beginning of line in the message body.
Once I fixed them, all messages are visible.
It looks like the rsync.mbox fi
Hello,
Rsync maintainers, could you evaluate the patches in Debian bugs #129135
and #124286? #129135 seems straightforward enough.
They are accessible at:
http://bugs.debian.org/129135
and
http://bugs.debian.org/124286
Also, I haven't gotten an evaluation of my patch for #128632 (previ
Platform: Compaq OpenVMS Alpha 7.3
Compiler: Compaq C T6.5
The following patch resolves compile problems with the checksum.c module.
The type (char) was being used where the usage indicated either (void)
or (unsigned char) should be used.
The const qualifier was added to impove compiler effici
Platform: Compaq OpenVMS Alpha 7.3
Compiler: Compaq C T6.5
The following patch resolves compile problems with the HLINK.C module.
The cast on function argument for the qsort() routine was wrong, and not
allowing the compile to complete.
When the function definiton of the hlink_compare() is c
Platform: Compaq OpenVMS Alpha 7.3
Compiler: Compaq C T6.5
The following patch resolves compile problems with the IO.C module.
The (char) type was being used where (void) was more appropriate based
on the actual use of the code.
The (char) type was also being used where the usage was actually
On 7 Jan 2002, "John E. Malmberg" <[EMAIL PROTECTED]> wrote:
> With the default warning level, some of the failures are silent, but can
> cause incorrect code to be generated.
>
> In particular, malloc() will be substituted for the built in alloca()
> macro, unless Tru64 has the alloca.h header
On Mon, 7 Jan 2002, Albert Chin wrote:
> On Sun, Jan 06, 2002 at 05:58:46PM -0600, John E. Malmberg wrote:
> > The following popt files need patches in order to compile using Compaq C
> > on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
> > ALPHA us
On Sun, Jan 06, 2002 at 05:58:46PM -0600, John E. Malmberg wrote:
> The following popt files need patches in order to compile using Compaq C
> on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
> ALPHA using Compaq C. Except for the alloca issue, these shoul
The following files need patches in order to compile using Compaq C
on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
ALPHA using Compaq C. These should work on any ANSI compliant compiler.
Operating System: OpenVMS ALPHA V7.3
Compiler: Compaq C T6.5
Compiler switches
The following zlib files need patches in order to compile using Compaq C
on OpenVMS. These should work on any ANSI compliant compiler.
Operating System: OpenVMS ALPHA V7.3
Compiler: Compaq C T6.5
Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE)
fnmatch.c and mdfour.c. Compaq C on
The following zlib files need patches in order to compile using Compaq C
on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
ALPHA using Compaq C. These should work on any ANSI compliant compiler.
Operating System: OpenVMS ALPHA V7.3
Compiler: Compaq C T6.5
Compiler
The following popt files need patches in order to compile using Compaq C
on OpenVMS. These patches should also be needed on a Tru64 or LINUX on
ALPHA using Compaq C. Except for the alloca issue, these should work on
any ANSI compliant compiler.
Operating System: OpenVMS ALPHA V7.3
Compiler
make things clearer -- all using the same rsync
engine under the hood.)
> I'd like to get some of the smaller patches in to stabilize 2.5 before
> we do this.
Sounds good to me.
> > P.S. Question -- is the enum { } of all the OPT_ variables in
> > options.c necessary any mo
like to get some of the smaller patches in to stabilize 2.5 before
we do this.
> P.S. Question -- is the enum { } of all the OPT_ variables in
> options.c necessary any more? It looks like it's not.
Why? They're used to link from long_options to the cases in
parse_arguments().
Here's a new version of my rsync-server-over-remote-shell patch:
- diffs (-u) against 2.5.0
- syntax for running rsync server over remote shell is
rsync [options] -e ssh source [user@]host::module[/dest]
rsync [options] -e ssh [user@]host::module[/source] dest
If you need different username
> sun/amdahl/unixware patch
All these are applied now. I changed the library routines to just
include rsync.h
--
Martin
On Thu, Nov 29, 2001 at 09:11:58AM +1100, Martin Pool wrote:
...
> > 1. remove AC_FUNC_MEMCMP from configure.in because it causes Sunos
> > 4.1.4 to die. memcmp() there fails the "8-bit clean" test, but it
> > doesn't matter because memcmp() in rsync is only used to test if
> > so
On 28 Nov 2001, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> Yes, I had seen it but haven't volunteered my build machines because the
> build servers download code to execute over the open internet using only
> an rsync server, which gives no assurance that it hasn't been spoofed.
> Hopefully after
On Wed, Nov 28, 2001 at 10:26:35AM +1100, Martin Pool wrote:
...
> I'm not sure if you've seen this:
>
> http://build.samba.org:80/build.pl?tree=rsync&function=Recent+Builds
>
> It's a pretty good tool, since I don't have direct access to (for
> example) a CRAY. The downside is that it requir
On 27 Nov 2001, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> 2.4.7 isn't released yet. Martin has put a lot of changes in the last week
> into CVS, and when I tried it yesterday it didn't compile anywhere but
> Linux. Today it looks a bit better but I still have problems on all my
> platforms exce
1 - 100 of 116 matches
Mail list logo
