Page 1 of 1

Where is Knoppmyth getting 0.18.2?

Posted: Sun Dec 04, 2005 5:58 pm
by Eduardo
Why does Knoppmyth seem to be at 0.18.2?

They just released another build (a26) the previous a22 was a "0.18.2-SVN" version (whatever the difference of that is).

Posted: Mon Dec 05, 2005 4:51 am
by Pablo
There is a branch of MythTV in SVN called release-0-18-fixes. As the name implies, this branch is bug fixes for the 0.18 release. This branch is sometimes called 0.18.2.

At one point, KnoppMyth attempted to use this branch and used the trunk release instead. This was the a22 release. Later, KnoppMyth used the branch release. This is the a26 release.

MiniMyth 0.18.1.x tracks this branch release.

Posted: Wed Dec 07, 2005 4:44 pm
by Eduardo
Pablo wrote:MiniMyth 0.18.1.x tracks this branch release.
So if I run my frontend off of this it would be compatible with Knopp's a26? Currrently I'm using your custom compiled a22 release (thanks again).

I still have video issues on my frontend, and would rather use the proper minimyth stream of releases. Plus my backend seems to freeze up under the a22 release as well, hoping a26 would fix that.

Posted: Thu Dec 08, 2005 4:17 am
by Pablo
Eduardo wrote:
Pablo wrote:MiniMyth 0.18.1.x tracks this branch release.
So if I run my frontend off of this it would be compatible with Knopp's a26? Currrently I'm using your custom compiled a22 release (thanks again).

I still have video issues on my frontend, and would rather use the proper minimyth stream of releases. Plus my backend seems to freeze up under the a22 release as well, hoping a26 would fix that.
That is what I have been led to believe, but I have not tried it, since I do not run a KnoppMyth backend.

In addition, last time I looked, there was no clear upgrade from a22 to a26, since this is actually a Myth version downgrade. Has this changed?

Posted: Thu Dec 08, 2005 5:53 am
by Eduardo
Pablo wrote:In addition, last time I looked, there was no clear upgrade from a22 to a26, since this is actually a Myth version downgrade. Has this changed?
Nope no upgrade path. I am willing to throw away my backend data entirely as it is not stable. Again tonight it froze up about 3 minutes before it was to record my wife's show (I'm not too popular :oops: ).

I've migrated data before, I dump the sql tables and then have to reformat the insert queries to match the new/old data structure. There is only a couple of tables that need migrating, markup, recorded. I scan through settings to grab any relevant stuff. All I really care about is my recording schedule, which is easy enough to create from scratch.

I have my data all on a seperate drive, so I will swap the OS/App harddrive and do an install and let you know. Just a pain to have to setup all the DHCP, TFTP and other stuff.

Maybe I'll boot minimyth off the old server, and quickly bring up a new backend just to see if they are compatible, that way I can avoid the TFTP and DHCP steps until later.