[gentoo-dev] Re: Pending mask of Qt3 and MythTV

[Doug Goldstein <cardoe@gentoo.org>]

On Sun, Feb 21, 2010 at 11:25 PM, Ben de Groot <yngwin@gentoo.org> wrote:
> Hi,
>
> As the Gentoo Qt team has announced six months ago, Qt3 is about to be
> masked now (see bug 283429). We sent another mail with a timeline at
> the end of December. Most of the issues surrounding the mask and
> removal of Qt3 have been solved. But we see ourselves confronted with
> one remaining issue: MythTV. Its current stable version uses Qt3, but
> there is a Qt4 version in testing. In all this time the MythTV
> maintainers have not taken any action.

Incorrect. You came to me a few months ago and I told you I would not
and will not have time to mess with the package at all. I think I've
made that clear in past mailing list posts, discussions we've had, and
on bugzilla. Many people have spoken up about the situation and time
and time again I've said "please, take over the package. It needs to
be stabilized and a new unstable bump needs to happen." You took one
of those times to create a ticket saying you'd stabilize it, then
deferred to me and the arch teams. 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.

I do not have my Gentoo commit machine up and running right now. I've
only got my MythTV machines running x86 and amd64 with MythTV running
~arch for a while now. So I ask you once again, PLEASE just mark it
stable. SOMEONE. And quit accusing anyone of inaction.

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. The problem stems from people either not reading the
instructions when MythTV tells them they need to take action and read
the update guide. Or people stupidly reading the upgrade guide,
thinking "oh I'll upgrade my DB early" and upgrading their DB and then
running their old version. A news item will probably do more harm than
good and will result in a lot of partial corruptions, which we already
have one person on the bug you guys made for the news item already
doing.

-- 
Doug Goldstein