john at fcs.uga.edu
Tue Apr 27 17:58:01 GMT 2004
I am seeing the exact same thing, same two checksums.
The earlier file has size of 511412 and the latter 511395.
Here is the difference:
diff -urN rsync-2.6.1_early/util.c rsync-2.6.1_late/util.c
--- rsync-2.6.1_early/util.c 2004-04-22 18:17:15.000000000 -0400
+++ rsync-2.6.1_late/util.c 2004-04-27 12:43:40.000000000 -0400
@@ -805,7 +805,6 @@
buf[rlen] = '\0';
- fprintf(stderr, "p:`%s'\n", buf);
On Tue, Apr 27, 2004 at 07:34:19PM +0200, Markus W.Weissmann wrote:
> Hi folks,
> I'm maintaining the darwinports port of rsync and I encountered the
> following strange thing:
> I updated our port which contains a md5 checksum on 27. April 16:36 GMT.
> Then some people had successfull builds (meaning the checksum was
> valid). But now its
> not anymore, it changed. I had a look at rsync-2.6.1.tar.gz from
> and the md5 still matches the file from there.
> The checksum I got first is
> md5 ec09e62961c8edd0f9d3710b5ecb5b16
> The file I just downloaded now has
> md5 6b1ee6a5878569215204f322ad128775
> whats going on???
More information about the rsync