| 1 |
On 02/22/2010 12:25 AM, Ben de Groot wrote: |
| 2 |
> If no action is taken soon, we see no other way than to protect the |
| 3 |
> users by masking the complete mythtv package. We hope this won't be |
| 4 |
> necessary. |
| 5 |
|
| 6 |
Agreed none of the options are nice. The mythtv wiki isn't a bad |
| 7 |
resource, how about this for a news item (I can commit if there are no |
| 8 |
objections - and be gentle as I just parsed the GLEP - also posted to |
| 9 |
the bug 299222): |
| 10 |
|
| 11 |
Title: MythTV 0.22 Upgrade Database Corruption |
| 12 |
Author: Richard Freeman <rich0@g.o> |
| 13 |
Content-Type: text/plain |
| 14 |
Posted: <date> |
| 15 |
Revision: 1 |
| 16 |
News-Item-Format: 1.0 |
| 17 |
Display-If-Installed: <media-tv/mythtv-0.22 |
| 18 |
|
| 19 |
Due to an incompatibility between MythTV 0.21 and the default Gentoo |
| 20 |
MySQL configuration, it is likely that long-time MythTV users will have |
| 21 |
databases with a mixture of locale encodings. If you upgrade to 0.22 |
| 22 |
without following these directions carefully, you could end up with a |
| 23 |
database that contains errors that are extremely difficult to fix. |
| 24 |
|
| 25 |
Please see the MythTV Upgrade Guide for instructions: |
| 26 |
|
| 27 |
http://wiki.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding |
| 28 |
|
| 29 |
Be sure to save a database backup before upgrading. Also, be sure to |
| 30 |
upgrade any other clients/backends you are using to 0.22 at the same |
| 31 |
time. The upgrade instructions need to be followed once per database - |
| 32 |
individual client/backend upgrades do not require these steps. |
Archives