From owner-freebsd-ports@FreeBSD.ORG Thu Oct 4 06:07:39 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73A3E16A420; Thu, 4 Oct 2007 06:07:39 +0000 (UTC) (envelope-from ade@lovett.com) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.freebsd.org (Postfix) with ESMTP id 4CE7213C4B6; Thu, 4 Oct 2007 06:07:39 +0000 (UTC) (envelope-from ade@lovett.com) Received: from inferno.canal.lovett.com ([172.16.32.23]:61589) by mail.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IdJs2-0001Wd-8U; Wed, 03 Oct 2007 23:07:38 -0700 In-Reply-To: <200710040753.53259.andy@athame.co.uk> References: <2E59F114-17D1-44D7-BE51-2093F6FD0FB3@freebsd.org> <200710040753.53259.andy@athame.co.uk> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2A425378-3910-45A6-B225-20E3FDA06E22@freebsd.org> Content-Transfer-Encoding: 7bit From: Ade Lovett Date: Wed, 3 Oct 2007 23:07:37 -0700 To: Andy Fawcett X-Mailer: Apple Mail (2.752.3) Sender: ade@lovett.com Cc: ports@freebsd.org, kde@freebsd.org, Ade Lovett Subject: Re: [kde-freebsd] x11/kdelibs3 and new cups breakage 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: Thu, 04 Oct 2007 06:07:39 -0000 On Oct 03, 2007, at 21:53 , Andy Fawcett wrote: > On Thursday 04 October 2007 06:32:27 Ade Lovett wrote: >> Looks like x11/kdelibs3 is suffering from the same new-cups issue >> that hit x11-toolkits/gtk20 - full log can be found at http:// >> tinderbox.lovett.com/errors/6-i386-bison/kdelibs-3.5.7_2.log >> >> Can someone with more kde-fu than myself fix this please? > > ports/116767 apparently has a fix, but I've not had time to check > it out yet. I've added it to my tinderbox and just fired off another build, we'll see what happens (it appears to patch cleanly at least). -aDe