Mailing List Archive: MythTV: Users

Advice on best way to proceed required

Index | Next | Previous | View Threaded

alan at chandlerfamily

Apr 26, 2012, 8:20 AM

Post #1 of 3 (330 views)
Permalink

Advice on best way to proceed required

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

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

gnassas at mac

Apr 26, 2012, 10:08 AM

Post #2 of 3 (315 views)
Permalink

Re: Advice on best way to proceed required [In reply to]

On 2012-04-26, at 11:20 AM, Alan Chandler <alan [at] chandlerfamily> wrote:

> 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)?

No, the back end won't touch that db so you'll either have to upgrade the back end or rollback the db upgrade. Typically a backup is made before an upgrade so it should be as easy as restoring that db dump. The wiki has info on this.

> Secondly, are there any Squeeze Backports of 0.25 to happen soon?

I see that Debian multimedia just added .25 packages to unstable so I guess in a few weeks they'll migrate to stable. Look here:

http://www.debian-multimedia.org/lurker/search/20120420.141723.00000000 [at] mythtv

> 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?

It's not too hard to pull down the .25 package sources and build them against your system if you know your way around Debian. Another approach is to temporarily set up an unstable chroot and install the backend into it but have it point to your db on the non-chroot system. That would hold you until a stable .25 package bubbles up.

> Fourthly, how does my database get updated these 35 schema versions - and can I do that without loosing my recording schedules?

When you started the .25 frontend it would have asked for permission to do the upgrade. All your schedules are still there but unusable until the be and db match.

I'd rollback the db upgrade and the desktop install and pin it until you're ready to upgrade the backend.

- George
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

raymond at wagnerrp

Apr 26, 2012, 10:15 AM

Post #3 of 3 (317 views)
Permalink

Re: Advice on best way to proceed required [In reply to]

On 4/26/2012 11:20, Alan Chandler wrote:
> 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)?

No.

> Secondly, are there any Squeeze Backports of 0.25 to happen soon?

Would have to ask the Debian packagers.

> 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?

Not hard. Download the source, ./configure, make, make install.

> Fourthly, how does my database get updated these 35 schema versions -
> and can I do that without loosing my recording schedules?

Any instance of 'mythtv-setup' will upgrade the database, and will ask
for permission before proceeding. The master backend only is allowed to
upgrade the database (not slave backends). If run from a terminal, it
will ask for permission before proceeding. If not, it will assume you
want to do so, and update anyway. When you update, it will first make a
dump of the existing database for recovery purposes, and the step
through all the changes needed to convert your database to current.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads