From owner-freebsd-ports@FreeBSD.ORG Fri Jan 23 08:25:31 2009 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 A4B1D106566C; Fri, 23 Jan 2009 08:25:30 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail.itac.at (mail.itac.at [213.47.211.116]) by mx1.freebsd.org (Postfix) with ESMTP id 0B7138FC08; Fri, 23 Jan 2009 08:25:29 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from localhost ([127.0.0.1] helo=webmail.itac.at) by mail.itac.at with esmtpa (Exim 4.63) (envelope-from ) id 1LQHLz-0005Pb-C4; Fri, 23 Jan 2009 09:25:27 +0100 Received: from 83.64.253.201 (proxying for unknown) (SquirrelMail authenticated user decke@bluelife.at) by webmail.itac.at with HTTP; Fri, 23 Jan 2009 09:25:27 +0100 (CET) Message-ID: <897158138253233bfd3e231de9fcd936.squirrel@webmail.itac.at> In-Reply-To: <49791F13.9090306@FreeBSD.org> References: <490B64FC.60608@FreeBSD.org> <20081104072440.GA44156@dereel.lemis.com> <49106BFF.9070305@FreeBSD.org> <1230742678.30559.29.camel@main.lerwick.hopto.org> <20081231174333.GA2839@soaustin.net> <495BBFFB.50808@FreeBSD.org> <496FBA3C.8020705@FreeBSD.org> <7f675262da5576a059ad2eb2becfbec5.squirrel@webmail.itac.at> <49791F13.9090306@FreeBSD.org> Date: Fri, 23 Jan 2009 09:25:27 +0100 (CET) From: Bernhard =?iso-8859-1?Q?Fr=F6hlich?= To: glarkin@FreeBSD.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-multimedia@freebsd.org, Bernhard =?iso-8859-1?Q?Fr=F6hlich?= , freebsd-ports@freebsd.org Subject: Re: Call for testers: MythTV 0.21 port upgrade 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: Fri, 23 Jan 2009 08:25:31 -0000 On Fri, January 23, 2009 2:36 am, Greg Larkin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bernhard Fröhlich wrote: >> On Thu, January 15, 2009 11:35 pm, Greg Larkin wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Greg Larkin wrote: >>>> Mark Linimon wrote: >>>>> On Wed, Dec 31, 2008 at 04:57:58PM +0000, Craig Butler wrote: >>>>>> Any updates on the 0.21 version of Mythtv ?? I see that we are >>>>>> still >>>>>> at >>>>>> 0.20 in ports >>>>> If there's progress on 0.21, someone needs to say so -- the 0.20 >>>>> version is already past its deletion date since it has been broken >>>>> for so long. I'll make the commit to change the date if there is. >>>>> mcl >>>> Hi all, >>>> >>>> I am currently working on the following MythTV-related PRs and plan to >>>> close them soon: >>>> >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/126343 >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127856 >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/127857 >>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419 >>>> >>>> Please don't delete multimedia/mythtv yet. The last PR above contains >>>> a >>>> patch to upgrade it to 0.21. >>>> >>>> Regards, >>>> Greg >>> Hello all of you MythTV supporters with the collective patience of the >>> universe! >>> >>> I recently committed mythtv-frontend (PR 127856) and mythtv-themes (PR >>> 127857), and please let me know if you see any problems with the >>> updates. >>> >>> There is still some work to be done on multimedia/mythtv, and I'm >>> tackling that next. >>> >>> Thanks again for your patience and feedback! >>> >> >> Yiiha, great to hear that :o) I will update and test as soon as time >> permits. >> >> Do you plan to update multimedia/mythtv to 0.21 or just fix it and leave >> it at 0.20? Because in the later case there is at least one open compile >> problem from Torfinn Ingolfsen that hasn't been tackled down yet. >> > > Hi Bernhard, > > I do plan to update multimedia/mythtv to 0.21, if at possible. This PR > (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128419) is a patch to > update 0.20, but is that the one that you're saying still has a compile > problem? That is good news and probably the better way to go. Yes that compile problem occured with that patch but was specific to 0.20 so you can forget about it and just move on. -- Bernhard Fröhlich http://www.bluelife.at/