From owner-freebsd-ports Sat Oct 21 12: 6:26 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 11FC237B4CF for ; Sat, 21 Oct 2000 12:06:25 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 726EE1E029 for ; Sat, 21 Oct 2000 15:06:24 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id PAA22126 for ; Sat, 21 Oct 2000 15:06:23 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id MAA13202; Sat, 21 Oct 2000 12:06:22 -0700 (PDT) Message-Id: <200010211906.MAA13202@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: ports@freebsd.org Subject: Distfile checker is a little off Date: Sat, 21 Oct 2000 12:06:22 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, The distfile checker is a little confused -- I've been making it more conservative since it almost nuked hub one day, but now it's not getting through all its work. This triggers another bug that the email sender can't tell the difference between "not checked" and "not there", which caused a lot of people to get email complaining about unfetchable ports. Please double-check the web page, and if it says something like http://glade.pn.org/glade-0.5.11.tar.gz: Not checked (Last actual result NEVER [checked 0 times since Wed Dec 31 16:00:00 1969 ]) then just ignore the email -- it's a bug. If I haven't gotten this fixed by the next time it's time to send out email then I'll just disable the emails. Sorry for the inconveniece! Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message