From owner-freebsd-ports Thu May 23 6:28:25 2002 Delivered-To: freebsd-ports@freebsd.org Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by hub.freebsd.org (Postfix) with ESMTP id A752037B416 for ; Thu, 23 May 2002 06:28:21 -0700 (PDT) Received: from sbcglobal.net wa1ter@smtp-send.myrealbox.com [64.175.106.2] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare via secured & encrypted transport (TLS); Thu, 23 May 2002 07:28:09 -0600 Message-ID: <3CEC8C0D.3010004@sbcglobal.net> Date: Thu, 23 May 2002 06:28:29 +0000 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020508 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-ports Subject: *Serious* problem with ports system today on -CURRENT [May 23] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I just posted two items about imake-4 which turned out to be false accusations. Doing a portupgrade of imake-4 filled up a gigabyte of disk before running out of space, so I assumed it was an imake-4 problem, but it's worse than that. The same thing now happens with all ports because the config process goes into an infinite loop and continues to fill up disk space with each iteration. I'm not sure what changed overnight, but I think (maybe) I saw either autoconf or automake get upgraded just before this problem started--sorry I can't be certain. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message