public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: No more mythtv for Gentoo users?
Date: Wed, 3 Mar 2010 18:49:19 +0000 (UTC)	[thread overview]
Message-ID: <hmmavf$2nc$1@dough.gmane.org> (raw)
In-Reply-To: 5bdc1c8b1003030958q29637a19j937b087fdd62b4fa@mail.gmail.com

On 2010-03-03, Mark Knecht <markknecht@gmail.com> wrote:
> On Wed, Mar 3, 2010 at 8:52 AM, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>> When upgrading a machine today, I saw a notice that mythtv 0.21 has
>> now been hardmasked. ??I think it's because it depends on an obsolte
>> version of Qt. ??Don't get me started on the royal PITA of requiring
>> that Qt be installed for a backend-only setup on a server.
>>
>> Since 0.21 and 0.23 is hardmasked, and mythv 0.22 is unstable on
>> everything except the amd64 platform, what's an X86 user to do?

> I think this is being handled badly but that sort of the way it is for
> a few days anyway. Shortly 0.22 will be unmasked as stable if it isn't
> already, but there are LOTS and LOTS of things we need to be careful
> about when changing or the Myth database will get messed up and
> possibly be unusable.

I read the instructions for fixing the broken database encoding, but
it appears mine is fine -- so updating to 0.22 won't be quite as
painful as it might have been.  I'll still have to re-build the
frontend, since 0.22 doesn't use a compatible protocol.

> It seems that a few devs can decide that something like qt3 is enough
> to force people to move forward. I've got 5 x64/amd64 frontends plus
> a backend PPC server. I'm not convinced they thought about this sort
> of mixed environment issue but that's the way it is.
>
> I am expecting that it's going to be a bad couple of weeks....
>
> I'd like to find some sort of sunset overlay for 0.21 but I haven't
> looked. Let me know if you go that way.

I'll probably try upgrading to 0.22.

-- 
Grant Edwards               grant.b.edwards        Yow! We're going to a
                                  at               new disco!
                              gmail.com            




  reply	other threads:[~2010-03-03 18:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 16:52 [gentoo-user] No more mythtv for Gentoo users? Grant Edwards
2010-03-03 17:58 ` Mark Knecht
2010-03-03 18:49   ` Grant Edwards [this message]
2010-03-03 19:49     ` [gentoo-user] " Mark Knecht
2010-03-03 20:30       ` Grant Edwards
2010-03-03 20:38         ` Mark Knecht
2010-03-04 17:08           ` I want my old Myth theme back! [WAS Re: [gentoo-user] Re: No more mythtv for Gentoo users?] Michael Sullivan
2010-03-04 17:35             ` Neil Bothwick
2010-03-03 17:59 ` [gentoo-user] No more mythtv for Gentoo users? Neil Bothwick
2010-03-03 18:23   ` Willie Wong
2010-03-03 20:07     ` Alan McKinnon
2010-03-03 21:56       ` stosss
2010-03-03 22:20       ` Willie Wong
2010-03-04  1:29         ` Neil Bothwick
2010-03-04  1:28       ` Neil Bothwick
2010-03-04  7:35         ` Alan McKinnon
2010-03-04  8:50           ` Roy Wright
2010-03-04 10:44         ` Alex Schuster
2010-03-04 13:17           ` Neil Bothwick
2010-03-03 20:05 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hmmavf$2nc$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox