Errors with MySQL 5.0

Bug #30593 reported by kacheng
28
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned
mythtv (Ubuntu)
Fix Released
Medium
Unassigned
Dapper
Won't Fix
Undecided
Unassigned

Bug Description

Mythtv problem with MySQL 5.0

MythTV does not work with MySQL 5.0 yet because one of the columns in the dd_schedule table is named "repeat" and MySQL 5.0 now uses "repeat" as a reserved word.

A mythtv-commits post at:
http://www.mail-archive.com/mythtv-commits%40mythtv.org/msg06827.html
says the solution is to rename "repeat" to "isrepeat" in the datadirect.cpp file.

Presumably this requires a rebuild of mythbackend and mythfilldatabase and an update in the repository.

An alternative solution might be to downgrade mysql-server to 4.1. However, this can't be easily done as mysql-server-5.0 is a dependency of mythtv.

Either the dependency needs to be broken, or the repositories updated.

kacheng (kacheng)
summary: + Mythtv problem with MySQL 5.0
kacheng (kacheng)
description: updated
Revision history for this message
Darik Horn (dajhorn) wrote :

I can confirm that the MythTV 0.18 schema is incompatible with MySQL 5. If dapper will ship with MySQL 5, then the MythTV package should be upgraded to the 0.19 release.

Revision history for this message
Darik Horn (dajhorn) wrote :

Why was this bug rejected?

Revision history for this message
kacheng (kacheng) wrote :

I'm not sure, either. I thought perhaps I did something wrong in the bug report, or perhaps because the MythTV packages are not supported (they are in universe if I recall correctly).

If this is the case, where would we report this bug?

Revision history for this message
Andrea Veri (av) wrote :

try to contact by email or irc a ubuntu bug squad member, he will help you
and it will give you some more istructions about this bug.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Please leave the 'Ubuntu' task as Rejected; there is already an open task on mythtv, which is where this bug belongs.

Revision history for this message
kacheng (kacheng) wrote :

This problem reconfirmed on Dapper Flight 7.

Changed in mythtv:
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Jorgensen (ajorg) wrote :

Crap, I wish I'd known about this bug. Now my mythtv box is hosed. Please fix this.

Revision history for this message
Paul Greidanus (paul-majestik) wrote :

mysql-server-5.0 is not a requirement.. mysql-server is the requirement, make sure you've got mysql-server-4.1 installed before you install mythtv-database and you're ok. I think a good solution would be to add mysql-server-4.1 specifically as a requirement would be a good idea.

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

> make sure you've got mysql-server-4.1 installed before you install
> mythtv-database and you're ok.

That wasn't the case for me. I had mythtv installed and mysql-server-4.1 but a dist-upgrade uninstalled it for me for whatever reason. I don't think it uninstalled mysql-server but it may have. Then when I installed mythtv it wasn't working because of this bug and that for whatever reason mysql-server-5.0 was installed.

But that doesn't matter, the point is that the dependency needs to be on mysql-server-4.1 NOT mysql-server. OR mythtv should be updated to 0.19.

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

Just to clarify: mysql-server is a package which depends on mysql-server-5.0. mysql-server is also satisfied by mysql-server-4.1 but an apt-get dist-upgrade will install mysql-server-5.0 for you if you already have mysql-server installed.

We really should just update to 0.19.1 though.

Revision history for this message
wberrier (wberrier) wrote :

I also ran into this. Installing Myth on breezy was a dream and I was quite surprised to find that it didn't work out of the box on Dapper.

Seems like either upgrading to 0.19 or changing the deps to require 4.1 is a pretty simple/easy solution.

Revision history for this message
chipmonk010 (chipmonk010) wrote :

I have created a source package with this problem fixed. Its curently in the REVU if anyone wants to try it: http://revu.tauware.de/details.py?upid=2541

Revision history for this message
Mario Limonciello (superm1) wrote :

The 0.20 Release in the repositories has introduced support for MySQL 5.0.

Changed in mythtv:
status: Confirmed → Fix Released
Revision history for this message
Andrew Jorgensen (ajorg) wrote :

Bug still exists in dapper.

Changed in mythtv:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.