{"id":532,"date":"2006-09-16T03:52:32","date_gmt":"2006-09-16T08:52:32","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/hoanga\/2006\/09\/16\/mythtv-mysql5-ubuntu-dapper-busted\/"},"modified":"2006-09-16T03:52:32","modified_gmt":"2006-09-16T08:52:32","slug":"mythtv-mysql5-ubuntu-dapper-busted","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/hoanga\/2006\/09\/16\/mythtv-mysql5-ubuntu-dapper-busted\/","title":{"rendered":"Mythtv + Mysql5 + Ubuntu Dapper = Busted"},"content":{"rendered":"

<\/a><\/p>\n

A little history…<\/h4>\n

I took another shot at getting mythtv setup again after trying it a few<\/p>\n

years ago and lashing myself a few times trying to get the ivtv driver<\/p>\n

patched into a mainline kernel. After a bit of work back then I got it<\/p>\n

working but times changed and I ended up using the machine for different<\/p>\n

purposes.<\/p>\n

Installing MythTV again…<\/h4>\n

Once again, I’ve decided to take another shot at a mythtv installation.<\/p>\n

This time I figured I’d piggyback onto a distribution that probably had<\/p>\n

packages for it available. My choice was Ubuntu Dapper. So I did the<\/p>\n

simple thing and tried:<\/p>\n

<\/p>\n

sudo apt-get install mythtv<\/p>\n

<\/em><\/p>\n

Trying to configure MythTV<\/h4>\n

And soon I had a mythtv installation almost setup. It seems that many<\/p>\n

of the Japanese patches have been merged into mythtv (Wow!) so I didn’t<\/p>\n

have to crawl all over the Japanese web space to figure out how to patch<\/p>\n

in Japanese patches to obscure_utility (TM) just to get this working.<\/p>\n

The first time I tried populating mythtv’s database with TV listing information<\/p>\n

I got errors siilar to:<\/p>\n

<\/p>\n

Malformed UTF-8 character (1 byte, need 3, after start byte 0xe7) at<\/p>\n

\/usr\/lib\/perl5\/vendor_perl\/5.8.8\/Date\/Manip.pm line 7167.<\/p>\n

<\/em><\/p>\n

Since I’m not a perl god nor am I intimately familiar with mythtv or any<\/p>\n

of its tools, I ended up searching on that error message and found a<\/p>\n

post<\/a> <\/p>\n

on a Japanese board basically saying this would not be a major problem<\/p>\n

with using mythtv in Japanese so I did what most people do… ignored it.<\/p>\n

After I got the base configuration done, I realized I’d be spending a lot<\/p>\n

of time not looking directly at this machine since it’s main job was to be<\/p>\n

a backend recording machine rather than a frontend so I installed mythweb<\/p>\n

to help me manage recordings:<\/p>\n

<\/p>\n

sudo apt-get install mythweb<\/p>\n

<\/em><\/p>\n

The Killer Problem settles in<\/h4>\n

This is where problems started coming in. After populating the TV listings<\/p>\n

database, mythweb still failed to show ANY listings whatsoever. Needless<\/p>\n

to say, this makes it a little hard to schedule watching anything.<\/p>\n

After waiting a few days to see if this was just a transient problem<\/p>\n

I still had no TV listings so I decided to search on it. What I found<\/p>\n

basically was Mysql 5 changed a keyword ‘repeat’ to a reserved word which<\/p>\n

OF COURSE mythtv relied on using in one of its tables. What this results<\/p>\n

in is a non-working setup for viewing TV listings on mythtv. This problem<\/p>\n

affects mythtv 0.18.x and the mythtv developers have basically said ‘upgrade’<\/p>\n

if you want to fix it. However the Ubuntu Dapper packages stay steady at<\/p>\n

0.18.x with a dependency on mysql-server which defaults to Mysql5. It seems<\/p>\n

there are updated packages in Edgy (Why the f’ is it always in the NEXT<\/p>\n

release rather than backported to THIS release????) but none for Dapper yet.<\/p>\n

I hope someone backports these packages. In the meantime, I’ll try to see<\/p>\n

if the updated packages build cleanly on Dapper for my own purposes.<\/p>\n

References<\/h4>\n