From owner-freebsd-ports@FreeBSD.ORG Fri Jan 14 06:19:02 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9399816A4CE for ; Fri, 14 Jan 2005 06:19:02 +0000 (GMT) Received: from mail2out.barnet.com.au (mail2out.barnet.com.au [202.83.176.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCEF643D1D for ; Fri, 14 Jan 2005 06:19:01 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail2out.barnet.com.au (Postfix, from userid 27) id 3BDD3707446; Fri, 14 Jan 2005 17:19:00 +1100 (EST) X-Viruscan-Id: <41E764540000848EE5C332@BarNet> Received: from mail2-auth.barnet.com.au (mail2.barnet.com.au [202.83.176.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) Authority" (verified OK)) by mail2.barnet.com.au (Postfix) with ESMTP id E909F707445; Fri, 14 Jan 2005 17:18:59 +1100 (EST) Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) Certificate Authority" (verified OK)) by mail2-auth.barnet.com.au (Postfix) with ESMTP id 6D1BF707444; Fri, 14 Jan 2005 17:18:59 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id 3679B6109; Fri, 14 Jan 2005 17:18:58 +1100 (EST) Date: Fri, 14 Jan 2005 17:18:58 +1100 From: Edwin Groothuis To: Kris Kennaway Message-ID: <20050114061858.GD1175@k7.mavetju> References: <20050114060711.GC19000@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050114060711.GC19000@xor.obsecurity.org> User-Agent: Mutt/1.5.6i cc: ports@FreeBSD.org Subject: Re: [ports-i386@FreeBSD.org: exim-doc-info-4.40 failed on i386 6] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 06:19:02 -0000 On Thu, Jan 13, 2005 at 10:07:11PM -0800, Kris Kennaway wrote: > FYI; can you please investigate and/or report to the developers? If > you are already aware of this problem but do not yet have a fix, > please mark the port BROKEN in the appropriate case, so that users do > not unexpectedly encounter it. Fixed -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/