From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] News item: 2010-03-01 MythTV 0.22 Upgrade Database Corruption
Date: Fri, 26 Feb 2010 13:06:28 +0100 [thread overview]
Message-ID: <e117dbb91002260406o3cac5be1h22cb2d8d11120dea@mail.gmail.com> (raw)
In-Reply-To: <b41005391002251952u1f2e8648w503033e0052164ba@mail.gmail.com>
---------- 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)
> ______________________________________________________
>
next prev parent reply other threads:[~2010-02-26 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Ben de Groot [this message]
2010-02-26 12:13 ` [gentoo-dev] " Richard Freeman
2010-03-01 14:24 ` Ben de Groot
2010-03-01 15:33 ` Richard Freeman
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=e117dbb91002260406o3cac5be1h22cb2d8d11120dea@mail.gmail.com \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@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