From abo@minkirri.apana.org.au Tue Apr 16 14:28:18 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 400EF81FAE; Tue, 16 Apr 2002 14:28:18 +1000 (EST) Date: Tue, 16 Apr 2002 14:28:18 +1000 To: Nikhil Jhingan Subject: Status report for librsync for pysync. Message-ID: <20020416042817.GA10036@minkirri.apana.org.au> References: <5.1.0.14.0.20020410205730.033b5080@131.103.204.244> <5.1.0.14.0.20020410205730.033b5080@131.103.204.244> <5.1.0.14.0.20020411165712.03878988@131.103.204.244> <20020411133105.GA32440@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020411133105.GA32440@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Content-Length: 1199 Lines: 28 X-IMAPbase: 1078185462 0000000116 Status: RO X-Status: X-Keywords: X-UID: 1 G'day Nikhil, This is the status report for the librsync Python extension for pysync development on 2002-04-16 Tuesday after 1 day's work. I have created the project, configured the development environment, and put in place support. My primary way of recording and reporting development will be a diary available at; http://minkirri.apana.org.au/~abo/projects/pysync/swf/librsync.diary However I will also send status update emails at each milestone or if any problem is encountered. At this stage I have not yet finnished phase one of getting librsync compiled and running with MSC. I hit problems with my development environment (see diary for details) which caused delays. However, these problems are now resolved and I should have it finnished and be well started on phase two by the end of today. I don't see this adversely affecting completion of other milestones. I will send you another email when I have completed the first milestone today, along with any details. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- From rproxy-devel-admin@lists.sourceforge.net Sat Apr 13 03:14:58 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 41BEC99662 for ; Sat, 13 Apr 2002 03:14:56 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16w442-000775-00; Fri, 12 Apr 2002 09:38:18 -0700 Received: from appsrv1.eol.ca ([205.189.152.19]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16w43C-0006wE-00 for ; Fri, 12 Apr 2002 09:37:26 -0700 Received: from xbox.fidalianetworks.com (static-3M-b1-169.highspeed.eol.ca [64.56.238.169]) by appsrv1.eol.ca (Postfix) with ESMTP id 7154E3656 for ; Fri, 12 Apr 2002 12:37:11 -0400 (EDT) Received: by xbox.fidalianetworks.com with Internet Mail Service (5.5.2653.19) id ; Fri, 12 Apr 2002 12:34:07 -0400 Message-ID: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> From: Derek Watson To: "'rproxy-devel@lists.sourceforge.net'" Subject: RE: [rproxy-devel] librsync on Windows anyone? MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 12 Apr 2002 12:34:00 -0400 Date: Fri, 12 Apr 2002 12:34:00 -0400 Content-Length: 2132 Lines: 64 Status: RO X-Status: A X-Keywords: X-UID: 2 OP: How is this project going for you? I have successfully built librsync-0.9.3 under Windows (MS Visual C++ 6.0) without too many problems. I wouldn't really call it a port, though -- I basically stripped out some header file references that weren't on my system (config.h, namely!) and excluded a couple C files that seemed superfluous (forget which ones) and did a build with only a couple warnings. I can't really tell you if ALL the functionality of the library works under windows (my build, anyway) but I can verify that these functions are working for me: rs_sig_file rs_loadsig_file rs_build_hash_table rs_delta_file rs_patch_file rs_sig_begin And maybe a few others. . . Let me know if any of you would like to have a look at my project file, I'd be happy to help out. -dw > -----Original Message----- > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au] > Sent: Tuesday, April 09, 2002 10:38 PM > To: rproxy-devel@lists.sourceforge.net > Cc: rproxy-users@lists.sourceforge.net > Subject: [rproxy-devel] librsync on Windows anyone? > > > G'day, > > Has anyone tried or had success with librsync on windows? I > assume there would be nothing particularly tricky with > getting something like rdiff running on windows without > resourting to cygwin, or am I an optimistic fool? I'm not sure, I haven't attempted a native build. Cygwin ain't that bad though :}. > I'm going to attempt this very soon. If I'm the first and hit > problems I'll be making fixes and submitting patches as > necisary. However, before I dig in, I thought I'd seek > hints/tips/advice to avoid problems and re-inventing the wheel. > > BTW, it's been pretty quiet in here... has devel discussion > moved elsewhere or is it just that rproxy has no problems :-) It's here, just quiet. Rob _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Tue Apr 16 13:54:25 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id EA83D81F83 for ; Tue, 16 Apr 2002 13:54:23 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xK2f-00009L-00; Mon, 15 Apr 2002 20:54:05 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xK1z-0008Rs-00 for ; Mon, 15 Apr 2002 20:53:24 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 8CF82563B2; Tue, 16 Apr 2002 13:53:12 +1000 (EST) To: Derek Watson Cc: "'rproxy-devel@lists.sourceforge.net'" Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020416035311.GB2965@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Tue, 16 Apr 2002 13:53:12 +1000 Date: Tue, 16 Apr 2002 13:53:12 +1000 Content-Length: 2108 Lines: 52 Status: RO X-Status: X-Keywords: X-UID: 3 On Fri, Apr 12, 2002 at 12:34:00PM -0400, Derek Watson wrote: > > OP: How is this project going for you? I have successfully built > librsync-0.9.3 under Windows (MS Visual C++ 6.0) without too many problems. > I wouldn't really call it a port, though -- I basically stripped out some > header file references that weren't on my system (config.h, namely!) and > excluded a couple C files that seemed superfluous (forget which ones) and > did a build with only a couple warnings. [...] > And maybe a few others. . . Let me know if any of you would like to have a > look at my project file, I'd be happy to help out. I'm currently working on it right now, and am trying to nut out the best "right way" to do this, with the end aim being MSC support rolled into the official librsync. It would be really nice if autoconf could handle i386-pc-win32-msc as a target platform :-) I've had a bit of a look at how other projects handle it. So far I don't think I've Options; 1) Use MS projects or an nmake Makefile, and manualy mantain anything that needs changing. Messy, as MSC changes become a seperate branch that needs regular merges etc. 2) Create and manually mantain Makefile.msc and config.h.msc. Nasty as these will require regular updating for Makefile.am->Makefile.in->Makefile and configure.in->config.h.in->config.h changes. 3) Create and manually mantain Makefile.msc.in and config.h.msc.in that generate Makefile.msc and config.h.msc. Also a bit nasty, but a bit better as it moves the merge a little up the chain to Makefile.am->Makefile.in and configure.in->config.h.in. 4) try and get Makefile.am and configure.in to somehow generate Makefile.msc and config.h.msc. hints or suggestions anyone? -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From bje@tooth.toronto.redhat.com Tue Apr 16 21:26:00 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from touchme.toronto.redhat.com (to-velocet.redhat.com [216.138.202.10]) by minkirri.apana.org.au (Postfix) with ESMTP id 966959AA77 for ; Tue, 16 Apr 2002 21:25:59 +1000 (EST) Received: from tooth.toronto.redhat.com (unknown [172.16.14.29]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 342D6B8013; Tue, 16 Apr 2002 07:25:51 -0400 (EDT) Received: (from bje@localhost) by tooth.toronto.redhat.com (8.11.6/8.11.6) id g3GBPRm06802; Tue, 16 Apr 2002 07:25:27 -0400 From: Ben Elliston MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15548.2599.138178.360545@tooth.toronto.redhat.com> Date: Tue, 16 Apr 2002 07:25:27 -0400 (EDT) To: abo@minkirri.apana.org.au (Donovan Baarda) Cc: Derek Watson , "'rproxy-devel@lists.sourceforge.net'" Subject: Re: [rproxy-devel] librsync on Windows anyone? In-Reply-To: <20020416035311.GB2965@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> X-Mailer: VM 6.75 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Content-Length: 651 Lines: 20 Status: RO X-Status: X-Keywords: X-UID: 4 >>>>> "Donovan" == Donovan Baarda writes: Donovan> I'm currently working on it right now, and am trying to nut out the best Donovan> "right way" to do this, with the end aim being MSC support rolled into the Donovan> official librsync. Donovan> It would be really nice if autoconf could handle i386-pc-win32-msc as a Donovan> target platform :-) It does: [bje@tooth bje]$ sh ~/config/config.sub windows32 i386-pc-windows32-msvcrt Donovan> hints or suggestions anyone? Autoconf also looks for `cl', the Microsoft command line C/C++ compiler. So what are the problems in building librsync, then? Ben From rproxy-devel-admin@lists.sourceforge.net Wed Apr 17 14:00:25 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id D6CF656516 for ; Wed, 17 Apr 2002 14:00:22 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xgby-0006WZ-00; Tue, 16 Apr 2002 21:00:02 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xgb6-0006Qc-00 for ; Tue, 16 Apr 2002 20:59:16 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 54C8089451; Wed, 17 Apr 2002 13:58:44 +1000 (EST) To: Ben Elliston Cc: "'rproxy-devel@lists.sourceforge.net'" Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020417035844.GA13151@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> <15548.2599.138178.360545@tooth.toronto.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15548.2599.138178.360545@tooth.toronto.redhat.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Wed, 17 Apr 2002 13:58:44 +1000 Date: Wed, 17 Apr 2002 13:58:44 +1000 Content-Length: 4029 Lines: 95 Status: RO X-Status: X-Keywords: X-UID: 5 On Tue, Apr 16, 2002 at 07:25:27AM -0400, Ben Elliston wrote: > >>>>> "Donovan" == Donovan Baarda writes: [...] > Autoconf also looks for `cl', the Microsoft command line C/C++ > compiler. So what are the problems in building librsync, then? First, I'm using the latest stable cygwin and MSVC++ 6.0 attempting to configure and compile librsync 0.9.5. I'm not that familiar with autoconf and automake, or even MSVC++. I assumed from my google searches that MSVC++ & auto* were not happy together, and that many projects (like Python, gimp, etc) use seperately maintained "projects" for compiling with MSVC++. But before I did that, I just tried a cygwin config+make. the config succeeded, but make failed with; gcc -DHAVE_CONFIG_H -I. -I. -I. -Wall -Wshadow -Wundef -Wwrite-strings -Wmissing -prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -Wcast-qual -Wcast-align -g -O2 -c hex.c -o hex.o hex.c:26: inttypes.h: No such file or directory make[2]: *** [hex.lo] Error 1 make[2]: Leaving directory /home/abo/src/librsync-msc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /home/abo/src/librsync-msc' make: *** [all-recursive-am] Error 2abo@NGAPA ~/src/librsync-msc It seems the inttypes.h header provided in libc6-dev on Debian is not available on cygwin. As inttypes.h is not available in MSVC either, It will need the same treatement. For the record, I found an answer to this via google at; http://www.stanford.edu/~bescoto/rdiff-backup/FAQ.html#windows Which fixed this problem, but I used the cleaner and simpler "cd /usr/lib; ln -sv sys/types.h inttypes.h" instead. Wouldn't a minor hickup like this be something that configure would normally sort out? Can the configure.in be "fixed" to deal with it? Attempting to configure and compile using MSVC++, I've done the following (as taken from an INSTALL.TXT for sourcenav); 1) started cygwin after setting MSVC environment with the command "C:\WINDOWS\COMMAND.COM /E:4096 /c C:\cygwin\msvcrt.bat" using this msvcrt.bat; call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\Vcvars32.bat" C:\cygwin\cygwin.bat 2) Set compiler environment variables and ran .configure using this configure.msc script; #!/bin/sh export CC=cl export CFLAGS="-Z7 -Od -MD" ./configure --host=windows32 --prefix='C:/Progra~1/librsync' The configure seems to work, except throws up a few nasties like "configure: warning: unsigned char seems to be 0 bytes. Expect trouble." The make fails with; /bin/sh ./libtool --mode=compile cl -DHAVE_CONFIG_H -I. -I. -I. -Z7 -Od -MD -I./popt -c base64.c cl -DHAVE_CONFIG_H -I. -I. -I. -Z7 -Od -MD -I./popt -c base64.c Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved. base64.c C:\PROGRA~1\MICROS~2\VC98\INCLUDE\string.h(61) : warning C4114: same type qualifier used more than once C:\PROGRA~1\MICROS~2\VC98\INCLUDE\sys/types.h(65) : error C2632: 'long' followed by 'long' is illegal make[2]: *** [base64.lo] Error 1 make[2]: Leaving directory /home/abo/src/librsync-msvcrt' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /home/abo/src/librsync-msvcrt' make: *** [all-recursive-am] Error 2 which is bizzar because it seems to be cl reporting a problem with the MSVC++ header files. I notice the librsync v0.9.5 configure was generated with autoconf v2.13, whereas cygwin has v2.52. My next step will be to regenerate configure using the newer autoconf. Any hints/suggestions welcome. If this fails I'm just grabbing the Python config.h and creating MSVC++ projects. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Wed Apr 17 15:39:40 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 2D0068944C for ; Wed, 17 Apr 2002 15:39:24 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xi9m-0007Z6-00; Tue, 16 Apr 2002 22:39:02 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xi8m-0007P9-00 for ; Tue, 16 Apr 2002 22:38:03 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id EA8FD894DE; Wed, 17 Apr 2002 15:37:20 +1000 (EST) To: Ben Elliston Cc: "'rproxy-devel@lists.sourceforge.net'" Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020417053720.GB13151@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> <15548.2599.138178.360545@tooth.toronto.redhat.com> <20020417035844.GA13151@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020417035844.GA13151@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Wed, 17 Apr 2002 15:37:20 +1000 Date: Wed, 17 Apr 2002 15:37:20 +1000 Content-Length: 1801 Lines: 42 Status: RO X-Status: X-Keywords: X-UID: 6 On Wed, Apr 17, 2002 at 01:58:44PM +1000, Donovan Baarda wrote: > On Tue, Apr 16, 2002 at 07:25:27AM -0400, Ben Elliston wrote: > > >>>>> "Donovan" == Donovan Baarda writes: > [...] > > Autoconf also looks for `cl', the Microsoft command line C/C++ > > compiler. So what are the problems in building librsync, then? [...] > I notice the librsync v0.9.5 configure was generated with autoconf v2.13, > whereas cygwin has v2.52. My next step will be to regenerate configure using > the newer autoconf. This got closer... I got past the last compile error, but it is now failing with; /bin/sh ./libtool --mode=compile cl -DHAVE_CONFIG_H -I. -I. -I. -Z7 -Od -MD -I./popt -c fileutil.c cl -DHAVE_CONFIG_H -I. -I. -I. -Z7 -Od -MD -I./popt -c fileutil.c Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved. fileutil.c fileutil.c(28) : fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory make[2]: *** [fileutil.lo] Error 1 make[2]: Leaving directory /home/abo/src/librsync-msvcrt' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /home/abo/src/librsync-msvcrt' make: *** [all-recursive-am] Error 2 Now I'm getting somewhere... It looks like I'll have to add some AC_CHECK_HEADERS stuff to config.in and put #ifdef HAVE_xxx_H wrappers around some #includes. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Thu Apr 18 01:06:17 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 533588ED47 for ; Thu, 18 Apr 2002 01:06:14 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xr0H-00070x-00; Wed, 17 Apr 2002 08:05:49 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xqZE-0003xI-00 for ; Wed, 17 Apr 2002 07:37:53 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id AA09C9B29E; Thu, 18 Apr 2002 00:37:43 +1000 (EST) To: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020417143743.GA1929@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> <15548.2599.138178.360545@tooth.toronto.redhat.com> <20020417035844.GA13151@minkirri.apana.org.au> <20020417053720.GB13151@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020417053720.GB13151@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Thu, 18 Apr 2002 00:37:43 +1000 Date: Thu, 18 Apr 2002 00:37:43 +1000 Content-Length: 2814 Lines: 61 Status: RO X-Status: X-Keywords: X-UID: 7 G'day again, I feel like I'm having a monolog here... anyone listening? I have everything compiling, just failing on the link. To get this far I've had to make small changes to some files that were unconditionaly including header files that configure was correctly determining as not available. With these headers missing, #defines for STDERROR_FILENO and X_OK had to be added at the appropriate places. I will submit a patch to librsync when I've got it all working. I am >< this far from having a proper autoconf + MSVC working. Please excuse the long cut-n-paste of error output but the best help I've had so far is google hits on list archives. I'm hoping this thread will lead to a conclusion that others can google-hit on in the future :-) I now have it to the point where I have compiled everything, and it's falling over on the link with; /bin/sh ./libtool --mode=link cl -Z7 -Od -MD -I./popt -o rdiff.exe rdiff.obj isprefix.obj popt/libpopt.a librsync.la -lcposix cl -Z7 -Od -MD -I./popt -o rdiff.exe rdiff.obj isprefix.obj popt/libpopt.a ./.libs/librsync.a -lcposix Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved. Command line warning D4002 : ignoring unknown option '-lcposix' Command line warning D4024 : unrecognized source file type 'popt/libpopt.a', object file assumed Command line warning D4024 : unrecognized source file type './.libs/librsync.a', object file assumed Microsoft (R) Incremental Linker Version 6.00.8168 Copyright (C) Microsoft Corp 1992-1998. All rights reserved. /out:rdiff.exe /debug /out:rdiff.exe rdiff.obj isprefix.obj popt/libpopt.a ./.libs/librsync.a rdiff.obj : error LNK2001: unresolved external symbol _snprintf librsync.a(trace.obj) : error LNK2001: unresolved external symbol _snprintf librsync.a(stats.obj) : error LNK2001: unresolved external symbol _snprintf libpopt.a(popt.obj) : error LNK2001: unresolved external symbol _alloca libpopt.a(poptparse.obj) : error LNK2001: unresolved external symbol _alloca libpopt.a(findme.obj) : error LNK2001: unresolved external symbol _alloca librsync.a(trace.obj) : error LNK2001: unresolved external symbol _vsnprintf rdiff.exe : fatal error LNK1120: 3 unresolved externals As far as I can tell, _snprint and _vsnprintf etc, are in the msvcrt.dll, which the -MD option should handle, right? Time to make an msp... -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Thu Apr 18 20:28:23 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 50DDF48F60 for ; Thu, 18 Apr 2002 20:28:21 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16y992-0000cS-00; Thu, 18 Apr 2002 03:28:04 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16y98f-0000Yz-00 for ; Thu, 18 Apr 2002 03:27:42 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 1A8229B36E; Thu, 18 Apr 2002 20:27:25 +1000 (EST) To: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020418102724.GB14159@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> <15548.2599.138178.360545@tooth.toronto.redhat.com> <20020417035844.GA13151@minkirri.apana.org.au> <20020417053720.GB13151@minkirri.apana.org.au> <20020417143743.GA1929@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020417143743.GA1929@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Thu, 18 Apr 2002 20:27:24 +1000 Date: Thu, 18 Apr 2002 20:27:24 +1000 Content-Length: 3066 Lines: 65 Status: RO X-Status: A X-Keywords: X-UID: 8 G'day again, I'm Cc'ing to the rdiff-backup list this time because they might be interested. I'm working on compiling librsync under MSVC++, leading eventualy to librsync Python extension (that works on Windows and unix) as part of pysync. On Thu, Apr 18, 2002 at 12:37:43AM +1000, Donovan Baarda wrote: [...] > I will submit a patch to librsync when I've got it all working. I am >< this > far from having a proper autoconf + MSVC working. I have still not succeeded with autoconf+MSVC, but I'm very close. However, I have successfuly compiled rdiff.exe using an MSVC++ project. I have followed the Python approach for doing this, as it is very non-intrusive to the normal unix code. I have a PCbuild/ directory off the root that contains the workspace and project, as well as any VC specific files, including a config.h built by running a script "configure.msc" under cygwin. The configure.msc script simply calls configure with options to use VC. I have put in the source root, as this is useful for doing a full autoconf make using VC under cygwin (when I get it working). Note that the configure provided with 0.9.5 needed to be re-generated using the autoconf v2.13 provided with cygwin for it to work. Some changes were necisary to some source files. I have tried to keep these to a minium, and wrapped them in appropriate #ifdefs where possible. Once I clean this up a bit I will be submitting a patch agains 0.9.5 (today or tomorrow). [...] > I now have it to the point where I have compiled everything, and it's > falling over on the link with; [...] > librsync.a(stats.obj) : error LNK2001: unresolved external symbol _snprintf > libpopt.a(popt.obj) : error LNK2001: unresolved external symbol _alloca > libpopt.a(poptparse.obj) : error LNK2001: unresolved external symbol _alloca > libpopt.a(findme.obj) : error LNK2001: unresolved external symbol _alloca > librsync.a(trace.obj) : error LNK2001: unresolved external symbol _vsnprintf > rdiff.exe : fatal error LNK1120: 3 unresolved externals > > As far as I can tell, _snprint and _vsnprintf etc, are in the msvcrt.dll, > which the -MD option should handle, right? For the record, I hit similar problems compiling as a VC project, but only for _alloca. This turns out to be resolved by using #includin in the appropriate places. I don't know why a header file would make a difference to linking, but maybe it's a C++ thing. I don't know why the cygwin autoconf make using VC had the other missing symbols, but I still have some things to resolve (like compile options) when compiling that way. I won't waste too much time on it though as I have the Python extension to worry about first. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 04:43:22 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 268824018A for ; Fri, 19 Apr 2002 04:43:20 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yGs3-0006po-00; Thu, 18 Apr 2002 11:43:03 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yGr6-0006ha-00 for ; Thu, 18 Apr 2002 11:42:05 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 9DD864018A; Fri, 19 Apr 2002 04:41:52 +1000 (EST) To: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020418184152.GA21144@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> <20020416035311.GB2965@minkirri.apana.org.au> <15548.2599.138178.360545@tooth.toronto.redhat.com> <20020417035844.GA13151@minkirri.apana.org.au> <20020417053720.GB13151@minkirri.apana.org.au> <20020417143743.GA1929@minkirri.apana.org.au> <20020418102724.GB14159@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020418102724.GB14159@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 04:41:52 +1000 Date: Fri, 19 Apr 2002 04:41:52 +1000 Content-Length: 809 Lines: 19 Status: RO X-Status: X-Keywords: X-UID: 9 On Thu, Apr 18, 2002 at 08:27:24PM +1000, Donovan Baarda wrote: [...] > Some changes were necisary to some source files. I have tried to keep these > to a minium, and wrapped them in appropriate #ifdefs where possible. Once I > clean this up a bit I will be submitting a patch agains 0.9.5 (today or > tomorrow). patch submitted on SF, along with comment re cygwin + MSVC. It's not 100% pretty, but it compiles rdiff.exe. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Thu Apr 18 01:09:35 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id F015478F26 for ; Thu, 18 Apr 2002 01:09:32 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xr3p-0007aE-00; Wed, 17 Apr 2002 08:09:29 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16xqek-0004eo-00 for ; Wed, 17 Apr 2002 07:43:35 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id E91889B29E; Thu, 18 Apr 2002 00:43:25 +1000 (EST) To: Derek Watson Cc: "'rproxy-devel@lists.sourceforge.net'" Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020417144325.GB1929@minkirri.apana.org.au> References: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <016527C5ACE2D51199300050BA18F3D201827B@xbox.fidalianetworks.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Thu, 18 Apr 2002 00:43:25 +1000 Date: Thu, 18 Apr 2002 00:43:25 +1000 Content-Length: 1460 Lines: 30 Status: RO X-Status: X-Keywords: X-UID: 10 On Fri, Apr 12, 2002 at 12:34:00PM -0400, Derek Watson wrote: > > OP: How is this project going for you? I have successfully built > librsync-0.9.3 under Windows (MS Visual C++ 6.0) without too many problems. > I wouldn't really call it a port, though -- I basically stripped out some > header file references that weren't on my system (config.h, namely!) and > excluded a couple C files that seemed superfluous (forget which ones) and > did a build with only a couple warnings. I have gone down the autoconf + MSVC path and have got it to the point where everything compiles, just doesn't link rdiff.exe yet. The header references _should_ have been ifdef protected. The config.h is autogenerated by the "configure" script, and contains definitions that enable/disable stuff (like those headers), based on what compiler/library capabilities it detects. > And maybe a few others. . . Let me know if any of you would like to have a > look at my project file, I'd be happy to help out. Yeah, I'm _very_ interested. This has been _much_ more effort than I ever imagined. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From robert.collins@itdomain.com.au Fri Apr 19 08:06:24 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from itdomain003.itdomain.net.au (unknown [203.63.157.208]) by minkirri.apana.org.au (Postfix) with ESMTP id 89D775EA02 for ; Fri, 19 Apr 2002 08:06:22 +1000 (EST) content-class: urn:content-classes:message Subject: RE: [rproxy-devel] librsync on Windows anyone? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Apr 2002 08:06:19 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rproxy-devel] librsync on Windows anyone? Thread-Index: AcHnCOeSImsEUKrsSbSOBUA37ah6ygAHFI4A From: "Robert Collins" To: "Donovan Baarda" , Content-Length: 758 Lines: 22 Status: RO X-Status: A X-Keywords: X-UID: 11 > -----Original Message----- > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au]=20 > Sent: Friday, April 19, 2002 4:42 AM > To: rproxy-devel@lists.sourceforge.net > Subject: Re: [rproxy-devel] librsync on Windows anyone? >=20 >=20 > On Thu, Apr 18, 2002 at 08:27:24PM +1000, Donovan Baarda wrote: [...] > > Some changes were necisary to some source files. I have=20 > tried to keep=20 > > these to a minium, and wrapped them in appropriate #ifdefs where=20 > > possible. Once I clean this up a bit I will be submitting a patch=20 > > agains 0.9.5 (today or tomorrow). >=20 > patch submitted on SF, along with comment re cygwin + MSVC.=20 > It's not 100% pretty, but it compiles rdiff.exe. Does a cygwin target build still work with the patch? Rob From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 13:10:20 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 8DB2E9B670 for ; Fri, 19 Apr 2002 13:10:18 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yOmi-0005Xe-00; Thu, 18 Apr 2002 20:10:04 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yOmc-0005SJ-00 for ; Thu, 18 Apr 2002 20:09:59 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 23F289B6C1; Fri, 19 Apr 2002 13:09:48 +1000 (EST) To: Robert Collins Cc: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020419030947.GA11868@minkirri.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 13:09:47 +1000 Date: Fri, 19 Apr 2002 13:09:47 +1000 Content-Length: 2982 Lines: 67 Status: RO X-Status: X-Keywords: X-UID: 12 On Fri, Apr 19, 2002 at 08:06:19AM +1000, Robert Collins wrote: > > > > -----Original Message----- > > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au] > > Sent: Friday, April 19, 2002 4:42 AM > > To: rproxy-devel@lists.sourceforge.net > > Subject: Re: [rproxy-devel] librsync on Windows anyone? > > > > > > On Thu, Apr 18, 2002 at 08:27:24PM +1000, Donovan Baarda wrote: [...] > > > Some changes were necisary to some source files. I have > > tried to keep > > > these to a minium, and wrapped them in appropriate #ifdefs where > > > possible. Once I clean this up a bit I will be submitting a patch > > > agains 0.9.5 (today or tomorrow). > > > > patch submitted on SF, along with comment re cygwin + MSVC. > > It's not 100% pretty, but it compiles rdiff.exe. > > Does a cygwin target build still work with the patch? Yes... actualy, I think this patch makes it work a bit more cleanly. There was one header file that cygwin doesn't have and this patch correctly wraps the include in an #ifdef. I did not need to change "configure.in" as it already checked for all the missing headers. With this patch you can compile librsync the following ways; 1) "configure; make" as usual on unix hosts. 2) "configure; make" on cygwin, using cygwin's gcc. 3) "configure CC=cl --build=windows32; make" using MSVC6's cl.exe compiler. Note that the link will fail with two unresolved symbols _snprintf and _vsnprintf. This can be fixed with "#define snprintf _snprintf" and "#define vsnprintf _vsnprintf" in the right place, but I have left this as an excersise for someone who knows the autoconf "right way" to do this. There might also be a way to solve it setting some compiler flags with CFLAGS= at the configure stage, but my brain is not MSVC6 compatible enough to know how. 4) Open the "PCbuild/PCbuild.dsw" workspace in MSVC6 and build the rdiff project. The first three options have configure build systems of i686-pc-linux-gnu, i386-pc-windows32-cygwin, and i386-pc-linux-msvcrt respectively. I will be the first to admit that my MSVC6 workspace is very basic, and the changes made are barely enough to get it compiling. Compiling under all platforms still produces a few warnings. However, I had the basic objective to just demonstrate librsync can compile and run using MSVC6. For those building under various architectures, I've noticed that "make clean" and "make distclean" do not remove "popt/libpot.a", so you will get nasty errors on linking when changing architectures if you don't manually remove it. Something else that needs fixing by an automake expert :-) -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rdiff-backup-admin@keywest.Stanford.EDU Thu Apr 18 10:57:21 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from keywest.Stanford.EDU (keywest.Stanford.EDU [171.64.112.177]) by minkirri.apana.org.au (Postfix) with ESMTP id 183D284293 for ; Thu, 18 Apr 2002 10:57:15 +1000 (EST) Received: from keywest.Stanford.EDU (localhost.localdomain [127.0.0.1]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3I0v5c22751; Wed, 17 Apr 2002 17:57:05 -0700 Received: from minkirri.apana.org.au (postfix@minkirri.apana.org.au [203.12.237.9]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3I0txc22726 for ; Wed, 17 Apr 2002 17:56:00 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 3FEA78E6D6; Thu, 18 Apr 2002 10:55:59 +1000 (EST) To: rdiff-backup@keywest.Stanford.EDU Subject: Compiling rdiff on Windows anyone? Message-ID: <20020418005558.GA3877@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rdiff-backup-admin@keywest.Stanford.EDU Errors-To: rdiff-backup-admin@keywest.Stanford.EDU X-BeenThere: rdiff-backup@keywest.Stanford.EDU X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Discussion list for rdiff-backup program List-Unsubscribe: , List-Archive: Date: Thu, 18 Apr 2002 10:55:59 +1000 Content-Length: 530 Lines: 13 Status: RO X-Status: X-Keywords: X-UID: 13 G'day, I've been doing battle with compiling rdiff on Windows using MSVC++ for three days now. Is there anyone on this list who has tried this? -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ Rdiff-backup mailing list Rdiff-backup@keywest.Stanford.EDU http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup From rdiff-backup-admin@keywest.Stanford.EDU Thu Apr 18 22:12:11 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from keywest.Stanford.EDU (keywest.Stanford.EDU [171.64.112.177]) by minkirri.apana.org.au (Postfix) with ESMTP id 72C7143927 for ; Thu, 18 Apr 2002 22:12:07 +1000 (EST) Received: from keywest.Stanford.EDU (localhost.localdomain [127.0.0.1]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3ICC4c25311; Thu, 18 Apr 2002 05:12:04 -0700 Received: from minkirri.apana.org.au (postfix@minkirri.apana.org.au [203.12.237.9]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3ICBac25288 for ; Thu, 18 Apr 2002 05:11:36 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 8F1FF40F77; Thu, 18 Apr 2002 22:11:26 +1000 (EST) To: rdiff-backup@keywest.Stanford.EDU, rproxy-devel@lists.sourceforge.net Subject: rdiff deltas not very good compared to pysync, why? Message-ID: <20020418121125.GD14159@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rdiff-backup-admin@keywest.Stanford.EDU Errors-To: rdiff-backup-admin@keywest.Stanford.EDU X-BeenThere: rdiff-backup@keywest.Stanford.EDU X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Discussion list for rdiff-backup program List-Unsubscribe: , List-Archive: Date: Thu, 18 Apr 2002 22:11:26 +1000 Content-Length: 2450 Lines: 56 Status: RO X-Status: X-Keywords: X-UID: 14 G'day, Just been doing some work on librsync for a Python extension, and noticed that it is producing deltas more than twice as big as pysync produces, using the same block size. I'm using the released v0.9.5 code. I'm using some test files I generated for pysync testing. These consist of a 256K random data "oldfile.bin", and a slightly larger "newfile.bin" that includes random edits (insert,replace,delete,copy) of "oldfile.bin". Because this is all random data, it doesn't compress. pyproxy can produce both rsync and xdelta style deltas. The xdelta results should be pretty close to optimal, so they make a good basis to compare against. The default block size for pyproxy is 1024, so I used "-b 1024" when running rdiff to force the same block size. The results I got were; Operation size ---------------------------------- source oldfile.bin 262144 target newfile.bin 325316 rdiff signature 3084 pyproxy sig 8090 pyproxy xdelta 103463 pyproxy rdelta 131389 rdiff delta 319252 As you can see, the "rdiff signature" was less than half the size of than "pysync sig". This is understandable, as pysync uses a Python pickled dict of dicts for it's sigfile format. However, the "rdiff delta" is more than two times the size of "pysync rdiff", and more than three times the optimal "pyproxy xdelta". Since pysync uses a pickled Python list of (offset,length) tupples and insert strings, I find this very surprising. None of these are faulty, as a "patch" by any of the tools uses the correct result. Note that pysync does use gzip context compression (compressing the whole data stream, including hits, but only including the compressed output of misses), and I don't thing rdiff does. However, in this case the input data was all random so compression has no effect. Compressing any of the inputs or outputs yeilds negligable change. I haven't examined the librsync code to figure out why yet, but I suspect that there might be a bug in the rolling checksums. There is certainly something wrong. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ Rdiff-backup mailing list Rdiff-backup@keywest.Stanford.EDU http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup From rdiff-backup-admin@keywest.Stanford.EDU Fri Apr 19 01:19:12 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from keywest.Stanford.EDU (keywest.Stanford.EDU [171.64.112.177]) by minkirri.apana.org.au (Postfix) with ESMTP id C8A5B904F6 for ; Fri, 19 Apr 2002 01:19:09 +1000 (EST) Received: from keywest.Stanford.EDU (localhost.localdomain [127.0.0.1]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3IFJ6c26024; Thu, 18 Apr 2002 08:19:06 -0700 Received: from minkirri.apana.org.au (postfix@minkirri.apana.org.au [203.12.237.9]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3IFIVc25956 for ; Thu, 18 Apr 2002 08:18:31 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id DCB3C904F6; Fri, 19 Apr 2002 01:18:28 +1000 (EST) To: "Shirish H. Phatak" Cc: rdiff-backup@keywest.Stanford.EDU, rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? Message-ID: <20020418151828.GH14159@minkirri.apana.org.au> References: <20020418121125.GD14159@minkirri.apana.org.au> <3CBED4D3.1090309@tacitnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CBED4D3.1090309@tacitnetworks.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rdiff-backup-admin@keywest.Stanford.EDU Errors-To: rdiff-backup-admin@keywest.Stanford.EDU X-BeenThere: rdiff-backup@keywest.Stanford.EDU X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Discussion list for rdiff-backup program List-Unsubscribe: , List-Archive: Date: Fri, 19 Apr 2002 01:18:28 +1000 Content-Length: 2182 Lines: 48 Status: RO X-Status: X-Keywords: X-UID: 15 On Thu, Apr 18, 2002 at 10:14:43AM -0400, Shirish H. Phatak wrote: > > Hi, > > Can I have a look at the test files? I believe my patch which > improves the size of deltas for sequences of matches is already in > 0.9.4+. This patch also fixed a rolling checksum bug. > > I am not very familliar with pysync, but I could definitely take a > look at the rdiff output to see if anything is obviously wrong. I've sent the files plus pysync itself to you directly. I have a few theories about things that might contribute to pysync doing better... pysync uses pure adler32 checksums for the rolling checksum, which may or may not be better than what rdiff uses. The signature is an adler32 keyed dictionary of md5sum keyed dictionarys containing offsets. This means that when there are rolling checksum collisions (two different blocks with same rolling checksum), pysync will compare md5sums against all blocks with that rolling checksum. rdiff might use what pysync's xdelta implementation uses instead; a mapping of rolling checksums to a single offset (and md4sum). What this means is rolling checksum collisions result in the coliding block "disapearing" as a potential match. A high level of rolling checksum collisions results in a high number of "misses" that could have been "matches". The reason pysync's xdelta implentation uses this simplified approach is xdelta uses a much smaller block size, and it automatically byte extends any match forwards and backwards as far as it can go. This means a few false misses have less impact, because they are picked up by the byte extending anyhow. There is a useful heuristic of favoring the earliest block when there is a collision, on the basis that extending matches forwards from the earlier match gives longer match sequences. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ Rdiff-backup mailing list Rdiff-backup@keywest.Stanford.EDU http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup From abo@minkirri.apana.org.au Fri Apr 19 15:55:26 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 74A6C9B8A2; Fri, 19 Apr 2002 15:55:24 +1000 (EST) Date: Fri, 19 Apr 2002 15:55:23 +1000 To: Nikhil Jhingan Cc: nik@insof.com Subject: Re: Status report for librsync for pysync. Message-ID: <20020419055520.GA16602@minkirri.apana.org.au> References: <5.1.0.14.0.20020410205730.033b5080@131.103.204.244> <5.1.0.14.0.20020410205730.033b5080@131.103.204.244> <5.1.0.14.0.20020411165712.03878988@131.103.204.244> <20020411133105.GA32440@minkirri.apana.org.au> <20020416042817.GA10036@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020416042817.GA10036@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Content-Length: 2444 Lines: 49 Status: RO X-Status: X-Keywords: X-UID: 16 G'day Nikhil, This is the second status report for the librsync Python extension for pysync development sent on 2002-04-19 Friday after 4 day's work. Appologies for for not sending a status update earlier. The first milestone of compiling librsync on Windows using MSVC6 was first achieved after three days. The better part of a fourth day was spent testing, cleaning up, and documenting it, so it was completed on Thursday 2002-04-18. The changes neccisary to compile librsync and rdiff.exe using MSVC++ were non-trivial and took much longer than I expected. This combined with the delays caused by the earlier problems with the development environment mean I am about 3 days behind schedule. I am not sure how this will affect our agreement, so we need to discuss it. I hope that the 3 days delay is acceptable and hope that the milestones and milestone payments are still in effect. I successfuly compiled the rdiff.exe program using MSVC++ and confirmed it worked identicly to the binary provided with Debian. I ran it through the same tests used to validate pysync and confirmed that it works correctly. Interestingly, these tests identified that pysync produces smaller deltas, so I suspect librsync's delta calculation could be improved. I posted this to the librsync development list and someone is looking at it. A patch against the official librsync v0.9.5 has been prepared and submitted at the librsync sourceforge page. This patch is also available at the SWF link below. If you have no web access, I can email it to you. I am currently working on the swig'ed wrapper for librsync. This wrapper will provide optimised md4sum and rolling checksum routines that can be used by the existing pysync implementation, even if the whole librsync implementation is not. I am still recording and reporting development in the diary "librsync.diary", and am keeping a mailbox "librsync.mail" with all correspondence related to this development. I am also keeping other framents of information gatherd as I go. This documentation constitutes the Software Working File (SWF) for this project. All of these are available at; http://minkirri.apana.org.au/~abo/projects/pysync/swf/ Looking forward to your responce... -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 16:41:25 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 965CC9B8DB for ; Fri, 19 Apr 2002 16:41:20 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yS4s-0004Sl-00; Thu, 18 Apr 2002 23:41:02 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yS45-0004It-00 for ; Thu, 18 Apr 2002 23:40:14 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 53C259B6CA; Fri, 19 Apr 2002 16:39:57 +1000 (EST) To: Robert Collins Cc: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020419063956.GA20970@minkirri.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 16:39:57 +1000 Date: Fri, 19 Apr 2002 16:39:57 +1000 Content-Length: 1022 Lines: 28 Status: RO X-Status: X-Keywords: X-UID: 17 On Fri, Apr 19, 2002 at 08:06:19AM +1000, Robert Collins wrote: > > > > -----Original Message----- > > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au] [...] > > patch submitted on SF, along with comment re cygwin + MSVC. > > It's not 100% pretty, but it compiles rdiff.exe. > > Does a cygwin target build still work with the patch? See my earlier post about this. BTW, the sourceforge project page has the bug tracker disabled. I know you guys are not using the SF CVS, but where do I report bugs? It would be nice to have a public place where things like "make disclean" not removing "popt/libpopt.a" can be reported. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 17:13:17 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 6E9348C907 for ; Fri, 19 Apr 2002 17:13:15 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16ySZs-0005Fy-00; Fri, 19 Apr 2002 00:13:04 -0700 Received: from fastmail.fm ([209.61.183.86]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16ySZ9-00053Q-00 for ; Fri, 19 Apr 2002 00:12:19 -0700 Received: from fastmail.fm (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id 4BA246D9C4 for ; Fri, 19 Apr 2002 02:12:15 -0500 (CDT) X-Epoch: 1019200335 X-Sasl-enc: MSjvPQWipVGwTT6TNL0DJg Received: from flare (ip68-101-156-150.sd.sd.cox.net [68.101.156.150]) by fastmail.fm (Postfix) with ESMTP id 2C10F6D9D5 for ; Fri, 19 Apr 2002 02:11:12 -0500 (CDT) Message-ID: <00d101c1e771$6c3025e0$0300a8c0@wsd.jowood.de> From: "Van Gale" To: References: <20020418121125.GD14159@minkirri.apana.org.au> Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 00:11:25 -0700 Date: Fri, 19 Apr 2002 00:11:25 -0700 Content-Length: 607 Lines: 18 Status: RO X-Status: A X-Keywords: X-UID: 18 Hi Donovan, I've noticed similar problem with rdiff. I wanted to put some test cases together to see what kind of saving rsync deltas would gain, and with rdiff the patch was almost always the same size as input files. I was going to resume that project soon and build my test files a little more carefully. Btw, have you tried to get pysync working with pyrex? This *might* be an excellent way to get better performance. Van Gale _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 19:17:44 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 67DEA9B8A0 for ; Fri, 19 Apr 2002 19:17:42 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yUWA-0002hB-00; Fri, 19 Apr 2002 02:17:22 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yUGd-0007XM-00 for ; Fri, 19 Apr 2002 02:01:20 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 9F16B50547; Fri, 19 Apr 2002 19:01:10 +1000 (EST) To: Van Gale Cc: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? Message-ID: <20020419090109.GA1536@minkirri.apana.org.au> References: <20020418121125.GD14159@minkirri.apana.org.au> <00d101c1e771$6c3025e0$0300a8c0@wsd.jowood.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00d101c1e771$6c3025e0$0300a8c0@wsd.jowood.de> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 19:01:10 +1000 Date: Fri, 19 Apr 2002 19:01:10 +1000 Content-Length: 1125 Lines: 26 Status: RO X-Status: X-Keywords: X-UID: 19 On Fri, Apr 19, 2002 at 12:11:25AM -0700, Van Gale wrote: > Hi Donovan, > > I've noticed similar problem with rdiff. I wanted to put some test cases > together to see what kind of saving rsync deltas would gain, and with rdiff > the patch was almost always the same size as input files. I was going to > resume that project soon and build my test files a little more carefully. That sounds like you had a really buggy version of rdiff. I know an earlier version had a serious bug in the rolling checksum calcs that would have caused this, but the 0.9.5 release fixed it. > Btw, have you tried to get pysync working with pyrex? This *might* be an > excellent way to get better performance. I'm not familiar with pyrex... what is it? -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Fri Apr 19 19:38:18 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 8EF279B9A5 for ; Fri, 19 Apr 2002 19:38:16 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yUqC-0004s2-00; Fri, 19 Apr 2002 02:38:04 -0700 Received: from fastmail.fm ([209.61.183.86]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yUpo-0004pj-00 for ; Fri, 19 Apr 2002 02:37:40 -0700 Received: from fastmail.fm (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id F346F6D9DA for ; Fri, 19 Apr 2002 04:37:37 -0500 (CDT) X-Epoch: 1019209057 X-Sasl-enc: IOhSxkONkAqDkqhE8V+4fg Received: from flare (ip68-101-156-150.sd.sd.cox.net [68.101.156.150]) by fastmail.fm (Postfix) with ESMTP id E103A6D9BE for ; Fri, 19 Apr 2002 04:37:36 -0500 (CDT) Message-ID: <01de01c1e785$e0b7e7e0$0300a8c0@wsd.jowood.de> From: "Van Gale" To: "rproxy-devel" References: <20020418121125.GD14159@minkirri.apana.org.au> <00d101c1e771$6c3025e0$0300a8c0@wsd.jowood.de> <20020419090109.GA1536@minkirri.apana.org.au> Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Fri, 19 Apr 2002 02:37:51 -0700 Date: Fri, 19 Apr 2002 02:37:51 -0700 Content-Length: 1144 Lines: 31 Status: RO X-Status: A X-Keywords: X-UID: 20 > That sounds like you had a really buggy version of rdiff. I know an earlier > version had a serious bug in the rolling checksum calcs that would have > caused this, but the 0.9.5 release fixed it. I was using 0.9.5, but my sample files might have had problems which is why I need to redo the tests with more care. > > Btw, have you tried to get pysync working with pyrex? This *might* be an > > excellent way to get better performance. > > I'm not familiar with pyrex... what is it? It's a language that looks very similar to Python with the addition of type declarations, but it compiles into a 'C' Python Extension Module. The idea is to eventually have a tool that makes it easier to convert Python code into a C extension for better performance. It's not quite there yet because it doesn't support list comprehensions or classes yet, which also means pysync would need a little rewriting. Anyway, see: http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/ Van _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From robert.collins@itdomain.com.au Fri Apr 19 21:47:18 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from itdomain003.itdomain.net.au (unknown [203.63.157.208]) by minkirri.apana.org.au (Postfix) with ESMTP id 4512C9B9B8 for ; Fri, 19 Apr 2002 21:47:17 +1000 (EST) content-class: urn:content-classes:message Subject: RE: [rproxy-devel] librsync on Windows anyone? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Apr 2002 21:47:15 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [rproxy-devel] librsync on Windows anyone? Thread-Index: AcHnT63kg0RfiQo4QH25/QKvloofRQASBiQQ From: "Robert Collins" To: "Donovan Baarda" Cc: Content-Length: 735 Lines: 26 Status: RO X-Status: A X-Keywords: X-UID: 21 > -----Original Message----- > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au]=20 > Sent: Friday, April 19, 2002 1:10 PM > Yes... actualy, I think this patch makes it work a bit more=20 > cleanly. There was one header file that cygwin doesn't have=20 > and this patch correctly wraps the include in an #ifdef. I=20 > did not need to change "configure.in" as it already checked=20 > for all the missing headers. >=20 > With this patch you can compile librsync the following ways; >=20 > 1) "configure; make" as usual on unix hosts. >=20 > 2) "configure; make" on cygwin, using cygwin's gcc. >=20 > 3) "configure CC=3Dcl --build=3Dwindows32; make" using MSVC6's=20 [...] Excellent. I hope this patch gets accepted... Rob From webform@vmware.com Fri Apr 19 23:59:31 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from geneva.vmware.com (geneva.vmware.com [63.93.12.3]) by minkirri.apana.org.au (Postfix) with ESMTP id 7947E9B9EA for ; Fri, 19 Apr 2002 23:59:28 +1000 (EST) Received: from pa-exch1.vmware.com (pa-exch1.vmware.com [172.16.12.136]) by geneva.vmware.com (8.9.3/8.9.3) with ESMTP id GAA11710 for ; Fri, 19 Apr 2002 06:59:21 -0700 Received: by pa-exch1.vmware.com with Internet Mail Service (5.5.2653.19) id ; Fri, 19 Apr 2002 06:59:18 -0700 Message-ID: <2CC5AC63B162D4119DE400B0D02153180361E025@pa-exch1.vmware.com> From: WebForm To: "'abo@minkirri.apana.org.au'" Subject: RE: VMware Support Request SR# 103803 Date: Fri, 19 Apr 2002 06:59:16 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Length: 331 Lines: 12 Status: RO X-Status: A X-Keywords: X-UID: 22 DO NOT CHANGE THE SUBJECT LINE if you want to respond to this email. Dear Donovan Baarda, Thank you for your response. One workaround we think may work, is to replace the mouse in the virtual machine with a Standard Mouse driver (or Standard with wheel). Let me know if this helps. Best Regards, Kris VMware Customer Service From rproxy-devel-admin@lists.sourceforge.net Sat Apr 20 00:38:37 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 1B79E9BAA8 for ; Sat, 20 Apr 2002 00:38:35 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yZWo-0001BC-00; Fri, 19 Apr 2002 07:38:22 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yZJK-0007T9-00 for ; Fri, 19 Apr 2002 07:24:27 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 824709BA92; Sat, 20 Apr 2002 00:24:16 +1000 (EST) To: Robert Collins Cc: rproxy-devel@lists.sourceforge.net Subject: Re: [rproxy-devel] librsync on Windows anyone? Message-ID: <20020419142416.GA15756@minkirri.apana.org.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Sat, 20 Apr 2002 00:24:16 +1000 Date: Sat, 20 Apr 2002 00:24:16 +1000 Content-Length: 1511 Lines: 40 Status: RO X-Status: X-Keywords: X-UID: 23 On Fri, Apr 19, 2002 at 09:47:15PM +1000, Robert Collins wrote: > > > > -----Original Message----- > > From: Donovan Baarda [mailto:abo@minkirri.apana.org.au] > > Sent: Friday, April 19, 2002 1:10 PM > > > Yes... actualy, I think this patch makes it work a bit more > > cleanly. There was one header file that cygwin doesn't have > > and this patch correctly wraps the include in an #ifdef. I > > did not need to change "configure.in" as it already checked > > for all the missing headers. > > > > With this patch you can compile librsync the following ways; > > > > 1) "configure; make" as usual on unix hosts. > > > > 2) "configure; make" on cygwin, using cygwin's gcc. > > > > 3) "configure CC=cl --build=windows32; make" using MSVC6's > > [...] > > Excellent. I hope this patch gets accepted... Accepted or not, it's available on the SF project page. Feel free to send any issues/suggestions/complaints to me and I'll update the patch as required. If it is not accepted, I'm prepared to update it to apply cleanly to the official releases whenever they happen (it's not going to take much work, if any). -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rproxy-devel-admin@lists.sourceforge.net Sat Apr 20 00:40:45 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 6C4109BAB3 for ; Sat, 20 Apr 2002 00:40:43 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yZYu-0001WJ-00; Fri, 19 Apr 2002 07:40:32 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 16yZU2-0000fm-00 for ; Fri, 19 Apr 2002 07:35:31 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id C7D989BA85; Sat, 20 Apr 2002 00:35:18 +1000 (EST) To: Van Gale Cc: rproxy-devel Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? Message-ID: <20020419143517.GB15756@minkirri.apana.org.au> References: <20020418121125.GD14159@minkirri.apana.org.au> <00d101c1e771$6c3025e0$0300a8c0@wsd.jowood.de> <20020419090109.GA1536@minkirri.apana.org.au> <01de01c1e785$e0b7e7e0$0300a8c0@wsd.jowood.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01de01c1e785$e0b7e7e0$0300a8c0@wsd.jowood.de> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenThere: rproxy-devel@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rproxy developer's discussion List-Unsubscribe: , List-Archive: X-Original-Date: Sat, 20 Apr 2002 00:35:17 +1000 Date: Sat, 20 Apr 2002 00:35:17 +1000 Content-Length: 1998 Lines: 44 Status: RO X-Status: X-Keywords: X-UID: 24 On Fri, Apr 19, 2002 at 02:37:51AM -0700, Van Gale wrote: > > That sounds like you had a really buggy version of rdiff. I know an > earlier > > version had a serious bug in the rolling checksum calcs that would have > > caused this, but the 0.9.5 release fixed it. > > I was using 0.9.5, but my sample files might have had problems which is why > I need to redo the tests with more care. > > > > Btw, have you tried to get pysync working with pyrex? This *might* be > an > > > excellent way to get better performance. > > > > I'm not familiar with pyrex... what is it? > > It's a language that looks very similar to Python with the addition of type > declarations, but it compiles into a 'C' Python Extension Module. The idea > is to eventually have a tool that makes it easier to convert Python code > into a C extension for better performance. It's not quite there yet because > it doesn't support list comprehensions or classes yet, which also means > pysync would need a little rewriting. Anyway, see: > > http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/ Thanks for that. It looks _very_ interesting. I think I will start playing with it very soon. Even if pysync couldn't be completely pyrex'ed, one of the next things I was going to try with it was moving the rolling checksum into C. Pyrex could do this _very_ easily. Pysync is going to have a swig'ed interface to librsync very soon. It's going to become the one-stop python rsync solution, with everything ranging from pure Python, to partial python/pyrex, through to librsync interface. I'm also adding reverse delta support very soon. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ rproxy-devel mailing list rproxy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rproxy-devel From rsync-admin@lists.samba.org Sun Apr 21 05:24:31 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by minkirri.apana.org.au (Postfix) with ESMTP id 6077A5CBDF for ; Sun, 21 Apr 2002 05:24:29 +1000 (EST) Received: from va.samba.org (localhost [127.0.0.1]) by lists.samba.org (Postfix) with ESMTP id 8B9AB4223; Sat, 20 Apr 2002 12:25:08 -0700 (PDT) Delivered-To: rsync@lists.samba.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by lists.samba.org (Postfix) with SMTP id 224E5417E for ; Sat, 20 Apr 2002 12:24:16 -0700 (PDT) Received: (qmail 88418 invoked by uid 1000); 20 Apr 2002 19:23:38 -0000 From: Jos Backus To: rsync@lists.samba.org Subject: Patch: update popt/ to 1.5.1 Message-ID: <20020420192338.GC6399@lizzy.catnook.com> Reply-To: jos@catnook.com Mail-Followup-To: rsync@lists.samba.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: rsync-admin@lists.samba.org Errors-To: rsync-admin@lists.samba.org X-BeenThere: rsync@lists.samba.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rsync user list List-Unsubscribe: , List-Archive: X-Original-Date: Sat, 20 Apr 2002 12:23:16 -0700 Date: Sat, 20 Apr 2002 12:23:16 -0700 Content-Length: 921 Lines: 24 Status: RO X-Status: A X-Keywords: X-UID: 25 This patch updates the files under popt/ to the latest vendor drop. The only change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed in case somebody decides to build rsync on that platform without using the port. I'm not happy about the wording in popt/README.rsync so I may change it. The patch is available at http://www.catnook.com/rsync-popt-1.5.1.patch Comments welcome! (Note that I will be losing DSL connectivity for a week any moment now while I switch providers.) -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html From ben@stanford.edu Mon Apr 22 07:50:07 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from folly.Stanford.EDU (unknown [128.12.181.87]) by minkirri.apana.org.au (Postfix) with ESMTP id 280FD77BAD for ; Mon, 22 Apr 2002 07:48:54 +1000 (EST) Received: (from ben@localhost) by folly.Stanford.EDU (8.11.6/8.11.6) id g3LLkAf03782; Sun, 21 Apr 2002 14:46:10 -0700 Message-Id: <200204212146.g3LLkAf03782@folly.Stanford.EDU> X-Url: http://www.stanford.edu/~bescoto/ X-Files: The Truth Is Out There X-Mailer: exmh version 2.5 with XEmacs 21 From: Ben Escoto To: abo@minkirri.apana.org.au (Donovan Baarda), rdiff-backup@keywest.Stanford.EDU Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? In-Reply-To: Your message of "Fri, 19 Apr 2002 01:18:28 +1000." <20020418151828.GH14159@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_779988256P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 21 Apr 2002 14:46:10 -0700 Sender: ben@stanford.edu Content-Length: 1086 Lines: 33 Status: RO X-Status: X-Keywords: X-UID: 26 --==_Exmh_779988256P Content-Type: text/plain; charset=us-ascii Sorry, but you won't get any help from me with rdiff. My knowledge of how it works is only theoretical. But I appreciate all the effort being done. Anything that makes rdiff better or more portable does the same to rdiff-backup. Also your plans for pysync look very interesting. It might be best in the long run if rdiff-backup used a python module instead of "rdiff" to do the file diff/sig/patch work, because then rdiff-backup could chroot for extra security without rdiff falling out of the path. There are of course some other considerations (presumably be some speed gains, but on the other hand maybe installation could become more difficult) but that seemed like the main one. -- Ben Escoto --==_Exmh_779988256P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Exmh version 2.5 01/15/2001 iD8DBQE8wzMg+owuOvknOnURAjH/AJ0XTAiljO322Jy7v0w28R5MX9IA3gCdEudB ZZ4ahoSqR2xxA7MCLZqBtZU= =AfCy -----END PGP SIGNATURE----- --==_Exmh_779988256P-- From rsync-admin@lists.samba.org Mon Apr 22 09:58:33 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from lists.samba.org (unknown [198.186.203.85]) by minkirri.apana.org.au (Postfix) with ESMTP id D21E780B5A for ; Mon, 22 Apr 2002 09:57:47 +1000 (EST) Received: from va.samba.org (localhost [127.0.0.1]) by lists.samba.org (Postfix) with ESMTP id F34A4453C; Sun, 21 Apr 2002 16:49:58 -0700 (PDT) Delivered-To: rsync@lists.samba.org Received: from minkirri.apana.org.au (minkirri.apana.org.au [203.12.237.9]) by lists.samba.org (Postfix) with ESMTP id 3EF2A4182 for ; Sun, 21 Apr 2002 16:42:40 -0700 (PDT) Received: by minkirri.apana.org.au (Postfix, from userid 1000) id CEBD4787CB; Mon, 22 Apr 2002 09:40:58 +1000 (EST) To: rsync@lists.samba.org Subject: Re: Patch: update popt/ to 1.5.1 Message-ID: <20020421234058.GA18728@minkirri.apana.org.au> References: <20020420192338.GC6399@lizzy.catnook.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420192338.GC6399@lizzy.catnook.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rsync-admin@lists.samba.org Errors-To: rsync-admin@lists.samba.org X-BeenThere: rsync@lists.samba.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rsync user list List-Unsubscribe: , List-Archive: X-Original-Date: Mon, 22 Apr 2002 09:40:58 +1000 Date: Mon, 22 Apr 2002 09:40:58 +1000 Content-Length: 1242 Lines: 27 Status: RO X-Status: X-Keywords: X-UID: 27 On Sat, Apr 20, 2002 at 12:23:16PM -0700, Jos Backus wrote: > This patch updates the files under popt/ to the latest vendor drop. The only > change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed > in case somebody decides to build rsync on that platform without using the > port. I'm not happy about the wording in popt/README.rsync so I may change it. > > The patch is available at > > http://www.catnook.com/rsync-popt-1.5.1.patch I have just submitted a patch against librsync that included changes to the popt included in it for cygwin and MSVC compatability. Near as I can tell the popt I was patching was v1.3. Do you (or anyone else) know if the 1.5.1 version fixes cygwin and MSVC compilation? (by MSVC I mean doing "configure CC=cl --build=windows32" in cygwin). Should I be submitting my changes somewhere else upstream? -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html From shirish@tacitnetworks.com Thu Apr 25 02:53:12 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from newton.tacitnetworks.com (unknown [160.79.96.162]) by minkirri.apana.org.au (Postfix) with ESMTP id C9D5A40436 for ; Thu, 25 Apr 2002 02:53:04 +1000 (EST) Received: from tacitnetworks.com (localhost.localdomain [127.0.0.1]) by newton.tacitnetworks.com (8.11.6/8.11.6) with ESMTP id g3OGqjk00303; Wed, 24 Apr 2002 12:52:49 -0400 Message-ID: <3CC6E2DD.40507@tacitnetworks.com> Date: Wed, 24 Apr 2002 12:52:45 -0400 From: "Shirish H. Phatak" Reply-To: shirish@tacitnetworks.com User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Donovan Baarda , rproxy-devel@lists.sourceforge.net, tomave@utu.fi, mbp@samba.org Cc: rdiff-backup@keywest.stanford.edu Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? References: <20020418121125.GD14159@minkirri.apana.org.au> Content-Type: multipart/mixed; boundary="------------020601070606010709070409" Content-Length: 5749 Lines: 150 Status: RO X-Status: X-Keywords: X-UID: 28 This is a multi-part message in MIME format. --------------020601070606010709070409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi all, I have been really backed up and could not get to this until today. Sorry for the delay. I am attaching a patch against anonymous cvs that should fix the patch size problem. The patch will also cleanly apply to the 0.9.5 tree. The problem was my fault, I forgot to roll out bytes I was skipping over as an optimization in rs_delta_scan to avoid recomputing the weak checksum. With this patch the size of the rdiff delta with Donovan's samples was 131091 bytes. Please let me know if this solves the problem. Incidently bugs with rolling checksums are most easily detected by using the --paranoia option in rdiff which will abort on the first mismatched sum; thanks to Markus for pointing this out. This patch also includes a memory leak fix for a scoop buffer leak (upto 16k per job with default parameters). I had submitted the fix earlier but it probably got lost. This will only affect those who are using librsync as a library in long running programs. Since there appears to be a dedicated group of users and lots of activity, maybe we can convince Martin to roll in these patches and make a new release? -Shirish Donovan Baarda wrote: >G'day, > >Just been doing some work on librsync for a Python extension, and noticed >that it is producing deltas more than twice as big as pysync produces, using >the same block size. I'm using the released v0.9.5 code. > >I'm using some test files I generated for pysync testing. These consist of a >256K random data "oldfile.bin", and a slightly larger "newfile.bin" that >includes random edits (insert,replace,delete,copy) of "oldfile.bin". Because >this is all random data, it doesn't compress. > >pyproxy can produce both rsync and xdelta style deltas. The xdelta results >should be pretty close to optimal, so they make a good basis to compare >against. > >The default block size for pyproxy is 1024, so I used "-b 1024" when running >rdiff to force the same block size. The results I got were; > >Operation size >---------------------------------- >source oldfile.bin 262144 >target newfile.bin 325316 >rdiff signature 3084 >pyproxy sig 8090 >pyproxy xdelta 103463 >pyproxy rdelta 131389 >rdiff delta 319252 > >As you can see, the "rdiff signature" was less than half the size of than >"pysync sig". This is understandable, as pysync uses a Python pickled dict >of dicts for it's sigfile format. > >However, the "rdiff delta" is more than two times the size of "pysync >rdiff", and more than three times the optimal "pyproxy xdelta". Since pysync >uses a pickled Python list of (offset,length) tupples and insert strings, I >find this very surprising. None of these are faulty, as a "patch" by any of >the tools uses the correct result. > >Note that pysync does use gzip context compression (compressing the whole >data stream, including hits, but only including the compressed output of >misses), and I don't thing rdiff does. However, in this case the input data >was all random so compression has no effect. Compressing any of the inputs >or outputs yeilds negligable change. > >I haven't examined the librsync code to figure out why yet, but I suspect >that there might be a bug in the rolling checksums. There is certainly >something wrong. > --------------020601070606010709070409 Content-Type: text/plain; name="librsync-delta-shift.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="librsync-delta-shift.patch" ? COPYING2 ? COPYING_delta ? COPYING_sig Index: delta.c =================================================================== RCS file: /cvsroot/librsync/delta.c,v retrieving revision 1.29 diff -u -r1.29 delta.c --- delta.c 8 Aug 2001 04:58:17 -0000 1.29 +++ delta.c 24 Apr 2002 16:19:25 -0000 @@ -164,8 +164,8 @@ rs_long_t match_where; int search_pos, end_pos; unsigned char *inptr = (unsigned char *) p; - uint32_t s1 = job->weak_sig & 0xFFFF; - uint32_t s2 = job->weak_sig >> 16; + unsigned s1 = job->weak_sig & 0xFFFF; + unsigned s2 = job->weak_sig >> 16; if (job->basis_len) { rs_log(RS_LOG_ERR, "somehow got nonzero basis_len"); @@ -190,8 +190,18 @@ for (search_pos = 0; search_pos <= end_pos; search_pos++) { size_t this_len = job->block_len; - /* Did we inherit the signature from rs_delta_match?*/ + /* Did we inherit the signature from rs_delta_match, if + * so we know this block won't match and we should simply + * skip the first char. + */ if (job->have_weak_sig < 0) { + /* advance by one; roll out the byte we just skipped over. */ + unsigned char a = inptr[search_pos]; + unsigned shift = a + RS_CHAR_OFFSET; + + s1 -= shift; + s2 -= this_len * shift; + job->weak_sig = (s1 & 0xffff) | (s2 << 16); job->have_weak_sig = 1; /* We already know that this block won't match!*/ continue; Index: job.c =================================================================== RCS file: /cvsroot/librsync/job.c,v retrieving revision 1.28 diff -u -r1.28 job.c --- job.c 9 Apr 2001 15:02:40 -0000 1.28 +++ job.c 24 Apr 2002 16:19:25 -0000 @@ -84,6 +84,9 @@ rs_result rs_job_free(rs_job_t *job) { + if (job->scoop_buf) + free(job->scoop_buf); + rs_bzero(job, sizeof *job); free(job); --------------020601070606010709070409-- From rdiff-backup-admin@keywest.Stanford.EDU Thu Apr 25 11:01:52 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from keywest.Stanford.EDU (keywest.Stanford.EDU [171.64.112.177]) by minkirri.apana.org.au (Postfix) with ESMTP id D11349F2F9 for ; Thu, 25 Apr 2002 11:01:46 +1000 (EST) Received: from keywest.Stanford.EDU (localhost.localdomain [127.0.0.1]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3P115c02495; Wed, 24 Apr 2002 18:01:05 -0700 Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3P10vc02464 for ; Wed, 24 Apr 2002 18:00:57 -0700 Received: by lists.samba.org (Postfix, from userid 1091) id 2C68C4551; Wed, 24 Apr 2002 18:02:14 -0700 (PDT) From: Martin Pool To: "Shirish H. Phatak" Cc: Donovan Baarda , rproxy-devel@lists.sourceforge.net, tomave@utu.fi, rdiff-backup@keywest.Stanford.EDU, rsync@lists.samba.org Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? Message-ID: <20020424180214.A28475@va.samba.org> Mail-Followup-To: "Shirish H. Phatak" , Donovan Baarda , rproxy-devel@lists.sourceforge.net, tomave@utu.fi, rdiff-backup@keywest.stanford.edu, rsync@lists.samba.org References: <20020418121125.GD14159@minkirri.apana.org.au> <3CC6E2DD.40507@tacitnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3CC6E2DD.40507@tacitnetworks.com>; from shirish@tacitnetworks.com on Wed, Apr 24, 2002 at 12:52:45PM -0400 X-GPG: 1024D/A0B3E88B: AFAC578F 1841EE6B FD95E143 3C63CA3F A0B3E88B Sender: rdiff-backup-admin@keywest.Stanford.EDU Errors-To: rdiff-backup-admin@keywest.Stanford.EDU X-BeenThere: rdiff-backup@keywest.Stanford.EDU X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Discussion list for rdiff-backup program List-Unsubscribe: , List-Archive: Date: Wed, 24 Apr 2002 18:02:14 -0700 Content-Length: 1143 Lines: 27 Status: RO X-Status: X-Keywords: X-UID: 29 On 24 Apr 2002, "Shirish H. Phatak" wrote: > Since there appears to be a dedicated group of users and lots of > activity, maybe we can convince Martin to roll in these patches and make > a new release? I have been really lax in supporting librsync for the last few months, because of a new job and taking over maintenance of rsync itself. Needless to say I'm delighted that people find it useful. I'd like it if Shirish and/or Donovan (or somebody else) could join in managing the package. I think it might be good to set up a small web site for librsync, as it seems at the moment there's more interest in librsync as distinct from rproxy. Even more important is to test and (if appropriate) merge the patches that have been sent in, and then make a new release. We can either keep it on samba.org or move to sourceforge or somewhere else; in either case I'll give you the appropriate access. Is anyone interested? -- Martin _______________________________________________ Rdiff-backup mailing list Rdiff-backup@keywest.Stanford.EDU http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup From shirish@tacitnetworks.com Thu Apr 25 11:46:36 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from newton.tacitnetworks.com (unknown [160.79.96.162]) by minkirri.apana.org.au (Postfix) with ESMTP id 158ED9F887 for ; Thu, 25 Apr 2002 11:46:32 +1000 (EST) Received: from tacitnetworks.com (localhost.localdomain [127.0.0.1]) by newton.tacitnetworks.com (8.11.6/8.11.6) with ESMTP id g3P1k9k02447; Wed, 24 Apr 2002 21:46:09 -0400 Message-ID: <3CC75FE1.804@tacitnetworks.com> Date: Wed, 24 Apr 2002 21:46:09 -0400 From: "Shirish H. Phatak" Reply-To: shirish@tacitnetworks.com User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.9) Gecko/20020311 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Pool , Donovan Baarda Cc: rproxy-devel@lists.sourceforge.net, tomave@utu.fi, rdiff-backup@keywest.stanford.edu, rsync@lists.samba.org Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? References: <20020418121125.GD14159@minkirri.apana.org.au> <3CC6E2DD.40507@tacitnetworks.com> <20020424180214.A28475@va.samba.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Length: 1567 Lines: 40 Status: RO X-Status: A X-Keywords: X-UID: 30 Hi Martin, I can definitely help in managing the librsync package, especially since I will be maintaining our local tree anyway. As of now, I don't have the resources to get the Windows stuff tested; however, I can handle the Unix side of things. Maybe Donovan would be interested in managing the Windows effort? I am fine with either Sourceforge or samba.org. I have used the former quite extensively during Intermezzo development, but most of my usage was CVS access, so I don't think either site would make much of a difference. -Shirish Martin Pool wrote: >On 24 Apr 2002, "Shirish H. Phatak" wrote: > >> Since there appears to be a dedicated group of users and lots of >>activity, maybe we can convince Martin to roll in these patches and make >>a new release? >> > >I have been really lax in supporting librsync for the last few months, >because of a new job and taking over maintenance of rsync itself. > >Needless to say I'm delighted that people find it useful. > >I'd like it if Shirish and/or Donovan (or somebody else) could join >in managing the package. I think it might be good to set up a >small web site for librsync, as it seems at the moment there's more >interest in librsync as distinct from rproxy. Even more important >is to test and (if appropriate) merge the patches that have been >sent in, and then make a new release. We can either keep it on >samba.org or move to sourceforge or somewhere else; in either case >I'll give you the appropriate access. > >Is anyone interested? > From rdiff-backup-admin@keywest.Stanford.EDU Fri Apr 26 08:22:42 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from keywest.Stanford.EDU (keywest.Stanford.EDU [171.64.112.177]) by minkirri.apana.org.au (Postfix) with ESMTP id E9BC1A7E09 for ; Fri, 26 Apr 2002 08:22:35 +1000 (EST) Received: from keywest.Stanford.EDU (localhost.localdomain [127.0.0.1]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3PMMRc07850; Thu, 25 Apr 2002 15:22:27 -0700 Received: from minkirri.apana.org.au (postfix@minkirri.apana.org.au [203.12.237.9]) by keywest.Stanford.EDU (8.11.2/8.11.2) with ESMTP id g3PML5c07822 for ; Thu, 25 Apr 2002 15:21:07 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 72D8AA7C8A; Fri, 26 Apr 2002 08:20:58 +1000 (EST) To: "Shirish H. Phatak" Cc: Martin Pool , rproxy-devel@lists.sourceforge.net, tomave@utu.fi, rdiff-backup@keywest.Stanford.EDU, rsync@lists.samba.org Subject: Re: [rproxy-devel] rdiff deltas not very good compared to pysync, why? Message-ID: <20020425222058.GA30410@minkirri.apana.org.au> References: <20020418121125.GD14159@minkirri.apana.org.au> <3CC6E2DD.40507@tacitnetworks.com> <20020424180214.A28475@va.samba.org> <3CC75FE1.804@tacitnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CC75FE1.804@tacitnetworks.com> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rdiff-backup-admin@keywest.Stanford.EDU Errors-To: rdiff-backup-admin@keywest.Stanford.EDU X-BeenThere: rdiff-backup@keywest.Stanford.EDU X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Discussion list for rdiff-backup program List-Unsubscribe: , List-Archive: Date: Fri, 26 Apr 2002 08:20:58 +1000 Content-Length: 1483 Lines: 32 Status: RO X-Status: X-Keywords: X-UID: 31 On Wed, Apr 24, 2002 at 09:46:09PM -0400, Shirish H. Phatak wrote: > Hi Martin, > > I can definitely help in managing the librsync package, especially > since I will be maintaining our local tree anyway. As of now, I don't > have the resources to get the Windows stuff tested; however, I can > handle the Unix side of things. Maybe Donovan would be interested in > managing the Windows effort? I am also interested in helping take over librsync mantainence. Ordinarily I'm a pure linux development person, but in this case I was sponsored by Accellion to do a Python wrapper that had to work under windows. I'm also pretty familiar with how the algo works from my work on Pysync. > I am fine with either Sourceforge or samba.org. I have used the > former quite extensively during Intermezzo development, but most of my > usage was CVS access, so I don't think either site would make much of a > difference. I really like a bug-tracker and the extra stuff SF gives you. I also find SF is a fairly centralised place for it all. However, if samba.org can provide the same facilities... -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- _______________________________________________ Rdiff-backup mailing list Rdiff-backup@keywest.Stanford.EDU http://keywest.Stanford.EDU/mailman/listinfo/rdiff-backup From abo@minkirri.apana.org.au Fri Apr 26 09:49:01 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 66516A7ECE; Fri, 26 Apr 2002 09:49:01 +1000 (EST) Date: Fri, 26 Apr 2002 09:49:01 +1000 To: Nikhil Jhingan Subject: Re: Status report for librsync for pysync. Message-ID: <20020425234901.GC30410@minkirri.apana.org.au> References: <5.1.0.14.0.20020425161606.03506750@202.79.69.184> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20020425161606.03506750@202.79.69.184> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Content-Length: 1004 Lines: 21 Status: RO X-Status: X-Keywords: X-UID: 32 On Thu, Apr 25, 2002 at 04:36:24PM +0800, Nikhil Jhingan wrote: > > Hi, ....no updates in your diary for last couple of days. Hope things are > going fine. Sorry for the lack of updates. My son was off school on Wednesday and Thursday was a public holiday in Aus so it turned into a family day. I'm back onto it now and am hoping to get it all wrapped up today. The only thing that might stop me is I also have to get my BAS (Buisness Activity Statement, an Australian tax thing that needs to be sent in quarterly) sent in today, and it might steal a bit of my time. If I don't get it finished today, I will certainly get it finished on the week end. On Monday I can send you an invoice, you can check out the work I've done, and we can organise payment. Appologies for the delay. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- From rsync-admin@lists.samba.org Sat Apr 27 19:42:14 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by minkirri.apana.org.au (Postfix) with ESMTP id 7A8828C42A for ; Sat, 27 Apr 2002 19:42:11 +1000 (EST) Received: from va.samba.org (localhost [127.0.0.1]) by lists.samba.org (Postfix) with ESMTP id 8E9EF4487; Sat, 27 Apr 2002 02:43:26 -0700 (PDT) Delivered-To: rsync@lists.samba.org Received: from minkirri.apana.org.au (minkirri.apana.org.au [203.12.237.9]) by lists.samba.org (Postfix) with ESMTP id 69B3A41AB for ; Sat, 27 Apr 2002 02:42:36 -0700 (PDT) Received: by minkirri.apana.org.au (Postfix, from userid 1000) id E836B46127; Sat, 27 Apr 2002 19:41:11 +1000 (EST) To: rproxy-devel@lists.sourceforge.net, rsync@lists.samba.org Subject: rsync md4sum code. Message-ID: <20020427094110.GA1053@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rsync-admin@lists.samba.org Errors-To: rsync-admin@lists.samba.org X-BeenThere: rsync@lists.samba.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rsync user list List-Unsubscribe: , List-Archive: X-Original-Date: Sat, 27 Apr 2002 19:41:10 +1000 Date: Sat, 27 Apr 2002 19:41:10 +1000 Content-Length: 1053 Lines: 24 Status: RO X-Status: X-Keywords: X-UID: 33 G'day, I've been working on a Python interface to librsync and have noticed that it uses md4sum code borrowed from Andrew Tridgell and Martin Pool that comes via rsync and was originally written for samba. Is there anything special about this code compared to the RSA md4sum code that can be found with libmd <"http://www.penguin.cz/~mhi/libmd/">? Python uses the RSA md5sum code for it's md5 module, and making a Python md4 module was as simple as "sed 's/\(md\)5/\14/i'" over the Python interface code. I'm contemplating some cleanup code hacking on librsync and was wondering if the samba based md4sum code was "better" than the RSA code, or if it is worth switching. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html From mbp@samba.org Sun Apr 28 08:31:30 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by minkirri.apana.org.au (Postfix) with ESMTP id 6A25298D30 for ; Sun, 28 Apr 2002 08:31:28 +1000 (EST) Received: by lists.samba.org (Postfix, from userid 1091) id 5FD90446E; Sat, 27 Apr 2002 15:32:47 -0700 (PDT) Date: Sat, 27 Apr 2002 15:32:47 -0700 From: Martin Pool To: Donovan Baarda Cc: rproxy-devel@lists.sourceforge.net, rsync@lists.samba.org Subject: Re: rsync md4sum code. Message-ID: <20020427153247.F11793@va.samba.org> Mail-Followup-To: Donovan Baarda , rproxy-devel@lists.sourceforge.net, rsync@lists.samba.org References: <20020427094110.GA1053@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020427094110.GA1053@minkirri.apana.org.au>; from abo@minkirri.apana.org.au on Sat, Apr 27, 2002 at 07:41:10PM +1000 X-GPG: 1024D/A0B3E88B: AFAC578F 1841EE6B FD95E143 3C63CA3F A0B3E88B Content-Length: 790 Lines: 20 Status: RO X-Status: A X-Keywords: X-UID: 34 On 27 Apr 2002, Donovan Baarda wrote: > G'day, > > I've been working on a Python interface to librsync and have noticed that it > uses md4sum code borrowed from Andrew Tridgell and Martin Pool that comes > via rsync and was originally written for samba. Tridge recently discovered a bug in that code that probably does not weaken the digest, but that may make it incompatible with standard MD4. Basically, tail-extension is not properly carried out for blocks that are a multiple of 64 bytes in size. I haven't had a chance yet to check how this affects rsync. If it does, I suppose we should evolve the protocol to fix it. There's not meant to be anything special about it. One of my TODO items was to replace it with a faster implementation. -- Martin From rsync-admin@lists.samba.org Sun Apr 28 13:06:54 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by minkirri.apana.org.au (Postfix) with ESMTP id EDCBEAD35A for ; Sun, 28 Apr 2002 13:06:51 +1000 (EST) Received: from va.samba.org (localhost [127.0.0.1]) by lists.samba.org (Postfix) with ESMTP id 4D4264361; Sat, 27 Apr 2002 20:08:10 -0700 (PDT) Delivered-To: rsync@lists.samba.org Received: from minkirri.apana.org.au (minkirri.apana.org.au [203.12.237.9]) by lists.samba.org (Postfix) with ESMTP id BD3EB4210 for ; Sat, 27 Apr 2002 20:07:37 -0700 (PDT) Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 5E886ACFEA; Sun, 28 Apr 2002 13:06:11 +1000 (EST) To: rproxy-devel@lists.sourceforge.net, rsync@lists.samba.org Subject: Re: rsync md4sum code. Message-ID: <20020428030610.GA20081@minkirri.apana.org.au> References: <20020427094110.GA1053@minkirri.apana.org.au> <20020427153247.F11793@va.samba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020427153247.F11793@va.samba.org> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Sender: rsync-admin@lists.samba.org Errors-To: rsync-admin@lists.samba.org X-BeenThere: rsync@lists.samba.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: rsync user list List-Unsubscribe: , List-Archive: X-Original-Date: Sun, 28 Apr 2002 13:06:10 +1000 Date: Sun, 28 Apr 2002 13:06:10 +1000 Content-Length: 2372 Lines: 48 Status: RO X-Status: A X-Keywords: X-UID: 35 On Sat, Apr 27, 2002 at 03:32:47PM -0700, Martin Pool wrote: > On 27 Apr 2002, Donovan Baarda wrote: > > G'day, > > > > I've been working on a Python interface to librsync and have noticed that it > > uses md4sum code borrowed from Andrew Tridgell and Martin Pool that comes > > via rsync and was originally written for samba. > > Tridge recently discovered a bug in that code that probably does not > weaken the digest, but that may make it incompatible with standard > MD4. Basically, tail-extension is not properly carried out for blocks > that are a multiple of 64 bytes in size. This would be nealy all blocks, as everyone would be using 2^n sized blocks where n>5. If you meant to say "...that are _not_ multiple of 64 bytes...", then I would dare to suggest fixing this would not hurt anybody, but definitely record the affects. > I haven't had a chance yet to check how this affects rsync. If it > does, I suppose we should evolve the protocol to fix it. > > There's not meant to be anything special about it. One of my TODO > items was to replace it with a faster implementation. I'm not sure how the RSA implementation compares speed-wise, but given it is more "correct", would there be major objections to replacing the samba md4 with the RSA one in librsync? I guess I should benchmark and publish results... There would be backwards compatability issues for librsync and rdiff, but I'm hoping that these can be dealt with simply, hopefully by just bumping the major version number and documenting the issue. librsync is not as widely used as rsync itself so I don't think it would matter that much. I think the RSA/libmd code is more "standard", and it would be wise for librsync at least to adopt the more widely used code. It is certainly nice that the md2, md4, and md5 API's are so interchangeable. The only reason not to would be licencing issues, but I would guess if Python can include it and be GPL compatible, then it should be OK. -- ---------------------------------------------------------------------- ABO: finger abo@minkirri.apana.org.au for more info, including pgp key ---------------------------------------------------------------------- -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html From rproxy-devel-admin@lists.sourceforge.net Sun Apr 28 23:49:18 2002 Return-Path: Delivered-To: abo@minkirri.apana.org.au Received: from usw-sf-list1.sourceforge.net (usw-sf-fw2.sourceforge.net [216.136.171.252]) by minkirri.apana.org.au (Postfix) with ESMTP id 447FDADBB1 for ; Sun, 28 Apr 2002 23:49:16 +1000 (EST) Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 171p30-00032Q-00; Sun, 28 Apr 2002 06:49:02 -0700 Received: from minkirri.apana.org.au ([203.12.237.9]) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 171p2U-0002ti-00 for ; Sun, 28 Apr 2002 06:48:31 -0700 Received: by minkirri.apana.org.au (Postfix, from userid 1000) id 49949ADBB1; Sun, 28 Apr 2002 23:48:15 +1000 (EST) To: rproxy-devel@lists.sourceforge.net, rsync@lists.samba.org Message-ID: <20020428134814.GB20081@minkirri.apana.org.au> References: <20020427094110.GA1053@minkirri.apana.org.au> <20020427153247.F11793@va.samba.org> <20020428030610.GA20081@minkirri.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020428030610.GA20081@minkirri.apana.org.au> User-Agent: Mutt/1.3.28i From: abo@minkirri.apana.org.au (Donovan Baarda) Subject: [rproxy-devel] Re: rsync md4sum code. Sender: rproxy-devel-admin@lists.sourceforge.net Errors-To: rproxy-devel-admin@lists.sourceforge.net X-BeenTh