From owner-freebsd-stable Sat May 16 15:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16434 for freebsd-stable-outgoing; Sat, 16 May 1998 15:09:37 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16420 for ; Sat, 16 May 1998 15:09:27 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA13092; Sat, 16 May 1998 15:09:16 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Joao Carlos Mendes Luis cc: stable@FreeBSD.ORG Subject: Re: Hello.....? Whomever broke -stable, are you going to fix it? In-reply-to: Your message of "Sat, 16 May 1998 17:39:47 -0300." <199805162039.RAA10056@roma.coe.ufrj.br> Date: Sat, 16 May 1998 15:09:16 -0700 Message-ID: <13089.895356556@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > OTOH: I noticed that last week's 2.2-980508-SNAP had some files in it's > /usr/ports/distfiles directory. The Brazilian mirror gets these files > weekely, and this week's files (2.2-980511-SNAP) still have that trash: Yep, this is even true for the release. :) It's due to the way that the ports tree is built and the distfiles not being cleaned out before doing so - a known problem whcih I simply haven't gotten around to fixing yet. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message