From owner-freebsd-ports Tue Apr 1 12:50:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA29164 for ports-outgoing; Tue, 1 Apr 1997 12:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA29158; Tue, 1 Apr 1997 12:50:03 -0800 (PST) Date: Tue, 1 Apr 1997 12:50:03 -0800 (PST) Message-Id: <199704012050.MAA29158@freefall.freebsd.org> To: freebsd-ports Cc: From: "Jordan K. Hubbard" Subject: Re: ports/3120: ghostscript-4.03 package broken ? Reply-To: "Jordan K. Hubbard" Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR ports/3120; it has been noted by GNATS. From: "Jordan K. Hubbard" To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: luigi@iet.unipi.it, FreeBSD-gnats-submit@freefall.FreeBSD.org, jkh@freebsd.org Subject: Re: ports/3120: ghostscript-4.03 package broken ? Date: Tue, 01 Apr 1997 12:43:45 -0800 > Huh? I checked the package on wcarchive (did check when the PR came > in -- should have closed it then) and checked it again just now. > "gzip -t" and "tar tvzf" has no problem with packages-2.2/All/tk-4.1.tgz. > > The checksum of the file in question is > > MD5 (tk-4.1.tgz) = 38f57b7d1e41ab793c15fe05480ef89e It doesn't match. I've checked this twice now and rsync does not re-send the file when it's been corrupted by a previous (rsync) transfer. I've now proven beyond a shadow of a doubt (since something like this also happened to me last time) that rsync is a piece of shit and doesn't work; I will no longer be using or recommending rsync for anything. Sigh. I guess it's back to "mirroring" with tar. Jordan