[mythtv-users] Advice on best way to proceed required

[Alan Chandler]

Hi

New to the list, so apologies if I break any conventions.  Not new to 
Mythtv though, as I have been using it for several years.

My setup is that I have a headless server at home running Debian Stable 
(right now that means Debian Squeeze), which includes the Debian 
Multimedia as part of its package source. It is not an option to upgrade 
to a later release of Debian as this server is key to lots of other 
services I run (mail, dns, web ...)

This installs Mythtv 0.24 for me. (I run myth-setup through ssh -X)

I watch TV, from my Desktop PC, running Debian Unstable.

Just recently, that meant that it installed a new version of the 
Frontend which has a version 0.25-dmo


Now when I startup the front end it says...

"This version of MythTV requires an updated database. (schema is 35 
versions behind).

Please run myth-setup or mythbackend to update your database"

followed by Database Host and name.  When I click on OK it exits.

As a temporary work around to this problem, I find the best approach is 
to use the streaming interface through Myth-Web - with the browser 
redirecting the output to vlc.  This still has disadvantages (if I view 
a stream currently being recorded, it finishes as soon as it gets to how 
far it had recorded up to when I started viewing the stream, and I have 
to restart and then manually figure out where I was before continuing).

I tried XMBC, but found the interface confusing and often got completely 
stuck - skipping forwards and backwards (which I do a lot, especially to 
skip adverts) was very slow, if it worked at all).

I am looking for a longer term solution.

Therefore some questions

Firstly, is there any way to continue with an 0.24 backend and a 0.25 
front end. (such as run some database update script)?
Secondly, are there any Squeeze Backports of 0.25 to happen soon?
Thirdly, how hard is it to compile from source, and if I do that are the 
dependant packages in Squeeze advanced enough to do so?
Fourthly, how does my database get updated these 35 schema versions - 
and can I do that without loosing my recording schedules?

Thanks in advance.



-- 
Alan Chandler
http://www.chandlerfamily.org.uk