From owner-freebsd-ports@FreeBSD.ORG Sun Feb 12 21:19:52 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5699B106566B for ; Sun, 12 Feb 2012 21:19:52 +0000 (UTC) (envelope-from olgeni@FreeBSD.org) Received: from mail.colby.tv (93-62-141-58.ip22.fastwebnet.it [93.62.141.58]) by mx1.freebsd.org (Postfix) with ESMTP id CAB1E8FC13 for ; Sun, 12 Feb 2012 21:19:51 +0000 (UTC) Received: from server.colby.local (localhost [127.0.0.1]) by server.colby.local (8.14.5/8.14.5) with ESMTP id q1CKmvdm045269; Sun, 12 Feb 2012 21:48:57 +0100 (CET) (envelope-from olgeni@FreeBSD.org) Received: from exchange.colby.local ([192.168.1.11] helo=exchange.colby.local) with IPv4:25 by server.colby.local; 12 Feb 2012 21:48:57 +0100 Received: from backoffice.colby.local ([192.168.1.56]) by exchange.colby.local over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 12 Feb 2012 21:48:57 +0100 Date: Sun, 12 Feb 2012 21:48:57 +0100 (CET) From: Jimmy Olgeni X-X-Sender: olgeni@backoffice.colby.local To: Stephen Montgomery-Smith In-Reply-To: <4F38225C.7020009@missouri.edu> Message-ID: References: <20120212193927.GA86426@troutmask.apl.washington.edu> <4F38225C.7020009@missouri.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-OriginalArrivalTime: 12 Feb 2012 20:48:57.0259 (UTC) FILETIME=[BD6B47B0:01CCE9C7] Cc: freebsd-ports@FreeBSD.org, Steve Kargl Subject: Re: Please test your commits X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Feb 2012 21:19:52 -0000 On Sun, 12 Feb 2012, Stephen Montgomery-Smith wrote: > You should report which version of FreeBSD you are using. It might have > tested OK for the committer, but not for you. I'm watching a tinderbox run right now and it seems to fail on i386 only; amd64 looks ok. I just sent a full log to the maintainer. -- jimmy