public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption
@ 2010-02-26  1:19 Ben de Groot
       [not found] ` <e117dbb91002251913v679322a4lcdfe41e9bc5141ab@mail.gmail.com>
  0 siblings, 1 reply; 5+ messages in thread
From: Ben de Groot @ 2010-02-26  1:19 UTC (permalink / raw
  To: gentoo-dev

I think this is good to go, let's get some comments from the list.

Ben


---------- Forwarded message ----------
From: Richard Freeman <rich0@gentoo.org>
Date: 24 February 2010 16:57
Subject: Re: [gentoo-dev] Re: Pending mask of Qt3 and MythTV
To: gentoo-dev@lists.gentoo.org

How about this revised news item:

Title: MythTV 0.22 Upgrade Database Corruption
Author: Richard Freeman <rich0@gentoo.org>
Content-Type: text/plain
Posted: 2010-03-01
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <media-tv/mythtv-0.22

Due to an incompatibility between MythTV 0.21 and the default Gentoo
MySQL configuration, it is likely that long-time MythTV users will
have databases with a mixture of locale encodings.  If you upgrade to
0.22 without following these directions carefully, you could end up
with a database that contains errors that are extremely difficult to
fix.

Note that not all mythtv users need to modify their databases, and
this should only be performed at the time of the upgrade.  The guide
below contains instructions that can be used to determine if this
problem pertains to you.

Please see the MythTV Upgrade Guide for instructions:

   http://wiki.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding

Be sure to save a database backup before upgrading.  Also, be sure to
upgrade any other clients/backends you are using to 0.22 at the same
time.  The upgrade instructions need to be followed once per database
- individual client/backend upgrades do not require these steps.

If you do run into problems with your upgrade, there is a forum thread
where you may be able to find help:

   http://forums.gentoo.org/viewtopic-t-816566-highlight-.html



^ permalink raw reply	[flat|nested] 5+ messages in thread

* [gentoo-dev] Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database  Corruption
       [not found]   ` <b41005391002251952u1f2e8648w503033e0052164ba@mail.gmail.com>
@ 2010-02-26 12:06     ` Ben de Groot
  2010-02-26 12:13       ` Richard Freeman
  0 siblings, 1 reply; 5+ messages in thread
From: Ben de Groot @ 2010-02-26 12:06 UTC (permalink / raw
  To: gentoo-dev

---------- Forwarded message ----------
From: Alec Warner <antarus@gentoo.org>
Date: 26 February 2010 04:52
Subject: Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption
To: Ben de Groot <yngwin@gentoo.org>
Cc: pr@gentoo.org


Is there a simple way for users to determine what client versions they may have?

-A

On Thu, Feb 25, 2010 at 7:13 PM, Ben de Groot <yngwin@gentoo.org> wrote:
> Forgot to send it to pr@
>
>
> ---------- Forwarded message ----------
> From: Ben de Groot <yngwin@gentoo.org>
> Date: 26 February 2010 02:19
> Subject: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption
> To: gentoo-dev@lists.gentoo.org
>
>
> I think this is good to go, let's get some comments from the list.
>
> Ben
>
>
> ---------- Forwarded message ----------
> From: Richard Freeman <rich0@gentoo.org>
> Date: 24 February 2010 16:57
> Subject: Re: [gentoo-dev] Re: Pending mask of Qt3 and MythTV
> To: gentoo-dev@lists.gentoo.org
>
> How about this revised news item:
>
> Title: MythTV 0.22 Upgrade Database Corruption
> Author: Richard Freeman <rich0@gentoo.org>
> Content-Type: text/plain
> Posted: 2010-03-01
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: <media-tv/mythtv-0.22
>
> Due to an incompatibility between MythTV 0.21 and the default Gentoo
> MySQL configuration, it is likely that long-time MythTV users will
> have databases with a mixture of locale encodings.  If you upgrade to
> 0.22 without following these directions carefully, you could end up
> with a database that contains errors that are extremely difficult to
> fix.
>
> Note that not all mythtv users need to modify their databases, and
> this should only be performed at the time of the upgrade.  The guide
> below contains instructions that can be used to determine if this
> problem pertains to you.
>
> Please see the MythTV Upgrade Guide for instructions:
>
>    http://wiki.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding
>
> Be sure to save a database backup before upgrading.  Also, be sure to
> upgrade any other clients/backends you are using to 0.22 at the same
> time.  The upgrade instructions need to be followed once per database
> - individual client/backend upgrades do not require these steps.
>
> If you do run into problems with your upgrade, there is a forum thread
> where you may be able to find help:
>
>    http://forums.gentoo.org/viewtopic-t-816566-highlight-.html
>
>
>
> --
> Ben de Groot
> Gentoo Linux developer (qt, media, lxde, desktop-misc)
> ______________________________________________________
>



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-dev] Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database   Corruption
  2010-02-26 12:06     ` [gentoo-dev] " Ben de Groot
@ 2010-02-26 12:13       ` Richard Freeman
  2010-03-01 14:24         ` Ben de Groot
  0 siblings, 1 reply; 5+ messages in thread
From: Richard Freeman @ 2010-02-26 12:13 UTC (permalink / raw
  To: gentoo-dev; +Cc: pr

On 02/26/2010 07:06 AM, Ben de Groot wrote:
> Is there a simple way for users to determine what client versions they may have?
>

Forwarding my reply:

Well, they can always just ask the package manager what version is 
installed.  The news item is targeted only at users who do not already 
have mythtv 0.22 installed, so only potentially impacted users will get 
the announcement.  The guide includes instructions for determining 
whether a particular database has problems.

mythfrontend also has a --version option that returns some useful 
information.

However, anybody getting the news item has a potential issue, and since 
mythtv isn't compatible across client versions if their gentoo install 
has a problem then all of their clients should need an upgrade.

Rich



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-dev] Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade  Database Corruption
  2010-02-26 12:13       ` Richard Freeman
@ 2010-03-01 14:24         ` Ben de Groot
  2010-03-01 15:33           ` Richard Freeman
  0 siblings, 1 reply; 5+ messages in thread
From: Ben de Groot @ 2010-03-01 14:24 UTC (permalink / raw
  To: gentoo-dev; +Cc: pr

The 72 hours have passed, so I take it we are ready to officially
publish this. Richard, are you going to commit this?

Thanks,
-- 
Ben de Groot
Gentoo Linux developer (qt, media, lxde, desktop-misc)
______________________________________________________



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-dev] Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption
  2010-03-01 14:24         ` Ben de Groot
@ 2010-03-01 15:33           ` Richard Freeman
  0 siblings, 0 replies; 5+ messages in thread
From: Richard Freeman @ 2010-03-01 15:33 UTC (permalink / raw
  To: Ben de Groot; +Cc: gentoo-dev, pr

On 03/01/2010 09:24 AM, Ben de Groot wrote:
> The 72 hours have passed, so I take it we are ready to officially
> publish this. Richard, are you going to commit this?
>

I will do so today.



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-03-01 15:34 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-26  1:19 [gentoo-dev] [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption Ben de Groot
     [not found] ` <e117dbb91002251913v679322a4lcdfe41e9bc5141ab@mail.gmail.com>
     [not found]   ` <b41005391002251952u1f2e8648w503033e0052164ba@mail.gmail.com>
2010-02-26 12:06     ` [gentoo-dev] " Ben de Groot
2010-02-26 12:13       ` Richard Freeman
2010-03-01 14:24         ` Ben de Groot
2010-03-01 15:33           ` Richard Freeman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox