summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt')
-rw-r--r--metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt35
1 files changed, 35 insertions, 0 deletions
diff --git a/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt b/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt
new file mode 100644
index 000000000000..71bf12826ec5
--- /dev/null
+++ b/metadata/news/2010-03-01-mythtv-upgrade/2010-03-01-mythtv-upgrade.en.txt
@@ -0,0 +1,35 @@
+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 using mysqldump 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
+