From owner-freebsd-ports@FreeBSD.ORG Mon Dec 15 17:50:10 2008 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 8A3C01065670 for ; Mon, 15 Dec 2008 17:50:10 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 5BB9E8FC16 for ; Mon, 15 Dec 2008 17:50:10 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id mBFHMnSw002153; Mon, 15 Dec 2008 11:22:49 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <49469295.2010309@math.missouri.edu> Date: Mon, 15 Dec 2008 11:23:33 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.18) Gecko/20081206 SeaMonkey/1.1.13 MIME-Version: 1.0 To: rotkap@gmx.de References: <20081206083250.GA54798@melon.esperance-linux.co.uk> <20081207.035520.258690873.hrs@allbsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: print/cm-super size mismatch 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: Mon, 15 Dec 2008 17:50:10 -0000 Heino Tiedemann wrote: > Hiroki Sato wrote: > >> Frank Shute wrote >> in <20081206083250.GA54798@melon.esperance-linux.co.uk>: >> >> fr> Hi, >> fr> >> fr> I just had a problem when building print/cm-super. >> >> This was because the distfile was updated. The port was also updated >> just now, so please try the latest ports tree. Thank you for the >> report! > > This Bug ist still There. > > I updated my ports collection, I deleteed all in my distfile folder -> > then I tried it today, und got this: I had this problem yesterday, when it was fixed last week. My guess is that that the bug is not "still there" but that it was "renewed." I am thinking that distfile was updated yet again. The odd thing was that even the distfile on the freebsd site was wrong. Shouldn't the distfile on the freebsd site be the one that the port wants, rather than whatever the master sites have? Stephen