From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NkJcg-0005nL-Hs for garchives@archives.gentoo.org; Wed, 24 Feb 2010 15:58:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 62531E0CBB; Wed, 24 Feb 2010 15:58:00 +0000 (UTC) Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by pigeon.gentoo.org (Postfix) with ESMTP id 2FFA1E0C35 for ; Wed, 24 Feb 2010 15:57:55 +0000 (UTC) Received: from gw.thefreemanclan.net ([unknown] [96.245.54.140]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KYC006R7SC3E030@vms173019.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Wed, 24 Feb 2010 09:57:44 -0600 (CST) Received: from [192.168.0.5] (rich.homedns.org [192.168.0.5]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by gw.thefreemanclan.net (Postfix) with ESMTPS id AE6171759FB3 for ; Wed, 24 Feb 2010 10:57:37 -0500 (EST) Message-id: <4B854C71.9040504@gentoo.org> Date: Wed, 24 Feb 2010 10:57:37 -0500 From: Richard Freeman User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100215 Thunderbird/3.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Pending mask of Qt3 and MythTV References: In-reply-to: Content-type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 6007dcb5-f319-4f6d-8fd3-4f67413f5d0f X-Archives-Hash: dd10b5efce46a7d798455b6b6fa9fe4b On 02/24/2010 02:15 AM, Doug Goldstein wrote: > My response was the arch teams haven't stabilized MythTV in years > because none of them have a setup to test it, so please stabilize it. > I'm running it on a stable machine. Well, to their credit, you CAN'T stabilize a package if you can't test it. I can test it and stabilize it on amd64, but that's it. If there is an arch that nobody has a mythtv setup for testing on then the solution is to drop the stable keyword entirely - not to just mark it stable. > As far as the news item goes, as I've said before. Its completely > unnecessary since MythTV will handle notifying you properly if you > need to do anything to your database. I can count more than a dozen > people on Gentoo that have successfully done the conversion without > issue. Here is the problem I have with this: doing the migration takes time. Somebody who does an emerge -u world probably doesn't set aside an hour or two to manually fix databases. Anybody doing this for mythtv will at best have a mythtv install that refuses to start until they spend time doing database dumps, sed scripts, and reloads. If for some reason the mythbacked doesn't detect the problem and starts up anyway, then they'll end up with partial database corruptions. I think that if nothing else we should send out a news item warning users that a major mythtv upgrade is coming and that they should exercise care in upgrading it, setting aside time for database cleanup if they are long-time users. I'm completely open to revised wording, but I don't feel comfortable stabilizing this for amd64 without any news at all. I do appreciate all you've done for mythtv, and the time crunch you are in right now. However, if I commit a keyword stabilization I need to be accountable for the results. I suspect the other arch teams feel similarly - nobody wants to just commit something like this without testing and good documentation. How about this revised news item: Title: MythTV 0.22 Upgrade Database Corruption Author: Richard Freeman Content-Type: text/plain Posted: Revision: 1 News-Item-Format: 1.0 Display-If-Installed: