Home » Forums » MythDora » Updating

0.22 RC1 on Mythdora 10.21

  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:746d89436a0a7daf08e696d6275150a7' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Has anyone tested 0.22 RC1 on Mythdora 10.21 64bit?</p>\n<p>If so please post your results and upgrade procedure</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:746d89436a0a7daf08e696d6275150a7' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:fba157a6ef3a64035d11337fb930df8c' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>I was waiting for the themes package to show up (just submitted by jarod today). Then I was going to post upgrade instructions.</p>\n<p>The intent right now is that we\'ll roll with 0.22 on 10.21 for a few months until we get 12.22 ready. </p>\n<p>Ryan</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:fba157a6ef3a64035d11337fb930df8c' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:50ff3b1daf5554e7494d2ef776f3c8d3' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Ryan</p>\n<p>Just read this on the Myth user list:</p>\n<p>\n<div class=\"quote-msg\">\n<div class=\"quote-author\">Quote:</div>\n<p>In case I haven\'t alluded clearly enough, the .22-&gt;.23 release cycle<br />\nwill be short. VERY short. You\'ll be surprised, just watch the<br />\nMythTV news around releasetime.\n</p></div>\n</p>\n<p>Maybe 10.21 upgraded to 0.22 will be enough to get to 12.23.</p>\n<p>Ben</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:50ff3b1daf5554e7494d2ef776f3c8d3' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:d56b0e13583c789784ce7a43567839c5' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Interesting.. I wonder what the .23 milestones are..</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:d56b0e13583c789784ce7a43567839c5' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:329d2a76211f4edd1d223f0175cb50ff' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>the roadmap for 0.23 has 1st March 2010 as the release date according to this:<br />\n<a href=\"http://svn.mythtv.org/trac/roadmap\">http://svn.mythtv.org/trac/roadmap</a></p>\n<p>Does that change the plans at all?</p>\n<p>Ben</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:329d2a76211f4edd1d223f0175cb50ff' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:a4c13ccc3f25e11d51b94fb9b53e0709' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>We\'ll see.. It may be that we do a 12.22 (with F12 due this month).. and then maybe a 12.23 following and single yum upgrade path between then.</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:a4c13ccc3f25e11d51b94fb9b53e0709' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:329e4bb4fa42151aac8f24629d75b587' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Sounds like a good plan.</p>\n<p>I tried an upgrade in a VM today and it appeared to work OK, so I am trying on a real (test) box at the moment.</p>\n<p>I basically used the instructions Jarod provided in the mythtv users list. I enabled the rpmfusion updates-testing repo and did a yum upgrade \\*myth\\*</p>\n<p>The only strange thing was when I installed the VM, there was no rpmfusion updates-testing repo, but there is on my real mythdora box, so I copied it over.</p>\n<p>Ben</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:329e4bb4fa42151aac8f24629d75b587' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:ca8d5416de87fa804f45769c69f4c3d4' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Guess I should have done the VM path (next time, Grrr). I\'m running a 64 bit system. After enabling rpmfusion updates-testing, I started with a full system update and couldn\'t get past that point (my system hasn\'t been updated for a long time - see Dennis, some of us listen - maybe that had something to do with it?). There were about 5 files duplicated between MD and rpmfusion test repos. Sorry, I don\'t have a copy of the file names any more. I started removing the first application listed form the MD repo and hosed the system. With no backup plan, I installed Fedora 11 last night and MythTV from rpmfusion test this morning and am going that path this time. I had to wipe my / and /boot mounts, during the install, but /storage mount still looks good, so I won\'t be much help this time for a 10.22 load. Yes, I did a full export of the .21 database schema for reference.</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:ca8d5416de87fa804f45769c69f4c3d4' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:e30f67f6a0ef20454ec2baf39d08d945' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Yeah it\'d be helpful if you would have kept track of the update issues. I\'ve got a 64bit vm host running now that I plan to use as a test base for the upgrade. </p>\n<p>I suspect the theme packages is one of the issues, but in terms of the rest of the conflicts.. I don\'t know where those may have come in. </p>\n<p>If at any time you added another repository (say atrpms) to your yum configuration, and didn\'t disable those when you issued update that maybe the cause.</p>\n<p>But to be clear for others that read this:</p>\n<p>You should not enable updates-testing and then do a yum update [all].. You should only be looking to get myth from updates-testing and not the other kernels, etc. </p>\n<p>And for general updating this would be preferred:</p>\n<p>yum --disablerepo=* --enablerepo=fedora,updates,rpmfusion-free,rpmfusion-free-updates,rpmfusion-nonfree,rpmfusion-nonfree-updates update</p>\n<p>So that it doesn\'t pull in from any other repos that may have been added (if any were). </p>\n<p>Ryan</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:e30f67f6a0ef20454ec2baf39d08d945' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:3c2e2424b00f405e67121b02f810e7aa' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Ryan,</p>\n<p> From your post on the main page about upgrading to .22, what should be done differently for those of us that run a separate BE and FE?</p>\n<p> I am not near my machine to see if I have the mythfrontend on my backend (I set it up as a back-end only during installation). I would assume we update the BE as per your instructions then do the same with the FE and then run the frontend to upgrade the database?</p>\n<p>Thanks for the help,<br />\nShredder</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:3c2e2424b00f405e67121b02f810e7aa' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:812dab4b73b47e9f0da8becfe5732ec9' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Actually.. If you launch the frontend from anywhere (provided the DB access is available). It should upgrade the schema. I upgraded my backend schema from frontend in the livingroom.</p>\n<p>Oh.. alternatively you can launch mythtv-setup and it\'ll upgrade the schema as well...</p>\n<p>Ryan</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:812dab4b73b47e9f0da8becfe5732ec9' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:fc0c5b5bac00dbeb775b846d944bc303' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Sweet. Thanks for the quick response. Hopefully I can try this out this weekend.</p>\n<p>Shredder</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:fc0c5b5bac00dbeb775b846d944bc303' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:e3a674f3a0be40456e413bf0fabef94e' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>I have been using MythTV for about 5 years now, intially via Fedora 3 (Thx Jarod) and then via MythDora (a very streamlined process to setup but gets outdated quickly due to 6 month release cycle of Fedora). Based on what I have read so far and seen, it makes more sense to part ways from Fedora and use a more LTS such as CentOS (CentTV anyone?).</p>\n<p>~~~~~~~~~~~~~~~~~~<br />\nMythdora v10.21 64-bit (MythTV v0.21-21) as of 9/13/2009.<br />\nN00b to Linux and MythDora. Prior minimal MythTV experience.</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:e3a674f3a0be40456e413bf0fabef94e' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:e01cca01ec67da7d2786889ec07d276f' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>~~~~~~~~~~~~~~~~~~<br />\nDowngraded to MythDora v10.22 x64 (seamless integration of external media player, subtitles from external srt/sub files are more important to me).</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:e01cca01ec67da7d2786889ec07d276f' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:0822f01f316721f75cbb3044329ca35e' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>You won\'t get any buy in from me. The problem with CentOS is that the kernel base is way old, and hardware support is often not up to snuff because of it.</p>\n<p>I update my systems fairly regularly.. but I really only do it when I need to fix something. For my mythtv hosts, I only keep them updated enough to do what I want. So the idea of a long term distro means very little to me. </p>\n<p>What exactly are you updating or what\'s the purpose of your updating exactly?</p>\n<p>Ryan</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:0822f01f316721f75cbb3044329ca35e' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:ffa15fdb7fb80f05a1b1c85d315f6f74' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>No flaming. But I agree with Ryan and support Fedora. You get newer hardware support and newer functionality faster. This allows me to upgrade to the newer cooler hardware faster when I want. If a system doesn\'t need an upgrade, it continues to run fine. <br />\nRecent fedora releases seem to be stable enough to just download MythTv from \"RPM fusion test\" and run stable. I have a BE:FE:mythweb setup on Fedora 11 and MythTV 22 RC1 running on a 64 bit test system. I just had to do one minor tewak to /etc/httpd/conf.d/mythweb.conf to get all working; I\'m looking forward to the upgrade procedure/download to migrate my main system. By the way, mythdora team, good work. It\'s appreciated.</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:ffa15fdb7fb80f05a1b1c85d315f6f74' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:2c97923bba766cfdaf022854e53aacc0' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>or will it be better to wait for Mythdora 11.22?</p>\n', created = 1369304775, expire = 1369391175, headers = '', serialized = 0 WHERE cid = '1:2c97923bba766cfdaf022854e53aacc0' in /var/www/mythdora/html/includes/cache.inc on line 109.
Submitted by RXM307 on October 15, 2009 - 9:58pm

Has anyone tested 0.22 RC1 on Mythdora 10.21 64bit?

If so please post your results and upgrade procedure

‹ Performance on RC .22 Yum update ›

I was waiting for the themes

Submitted by pisani on October 19, 2009 - 11:38am.

I was waiting for the themes package to show up (just submitted by jarod today). Then I was going to post upgrade instructions.

The intent right now is that we'll roll with 0.22 on 10.21 for a few months until we get 12.22 ready.

Ryan

»

Ryan Just read this on the

Submitted by benh on October 22, 2009 - 2:10pm.

Ryan

Just read this on the Myth user list:

Quote:

In case I haven't alluded clearly enough, the .22->.23 release cycle
will be short. VERY short. You'll be surprised, just watch the
MythTV news around releasetime.

Maybe 10.21 upgraded to 0.22 will be enough to get to 12.23.

Ben

»

Interesting.. I wonder what

Submitted by pisani on October 22, 2009 - 2:21pm.

Interesting.. I wonder what the .23 milestones are..

»

roadmap for 0.23

Submitted by benh on October 31, 2009 - 11:12pm.

the roadmap for 0.23 has 1st March 2010 as the release date according to this:
http://svn.mythtv.org/trac/roadmap

Does that change the plans at all?

Ben

»

We'll see.. It may be that

Submitted by pisani on October 31, 2009 - 11:17pm.

We'll see.. It may be that we do a 12.22 (with F12 due this month).. and then maybe a 12.23 following and single yum upgrade path between then.

»

Sounds like a good plan. I

Submitted by benh on October 21, 2009 - 3:02am.

Sounds like a good plan.

I tried an upgrade in a VM today and it appeared to work OK, so I am trying on a real (test) box at the moment.

I basically used the instructions Jarod provided in the mythtv users list. I enabled the rpmfusion updates-testing repo and did a yum upgrade \*myth\*

The only strange thing was when I installed the VM, there was no rpmfusion updates-testing repo, but there is on my real mythdora box, so I copied it over.

Ben

»

Are you running a 32 bit or a 64 bit system?

Submitted by hball01 on October 21, 2009 - 7:39am.

Guess I should have done the VM path (next time, Grrr). I'm running a 64 bit system. After enabling rpmfusion updates-testing, I started with a full system update and couldn't get past that point (my system hasn't been updated for a long time - see Dennis, some of us listen - maybe that had something to do with it?). There were about 5 files duplicated between MD and rpmfusion test repos. Sorry, I don't have a copy of the file names any more. I started removing the first application listed form the MD repo and hosed the system. With no backup plan, I installed Fedora 11 last night and MythTV from rpmfusion test this morning and am going that path this time. I had to wipe my / and /boot mounts, during the install, but /storage mount still looks good, so I won't be much help this time for a 10.22 load. Yes, I did a full export of the .21 database schema for reference.

»

Yeah it'd be helpful if you

Submitted by pisani on October 21, 2009 - 3:00pm.

Yeah it'd be helpful if you would have kept track of the update issues. I've got a 64bit vm host running now that I plan to use as a test base for the upgrade.

I suspect the theme packages is one of the issues, but in terms of the rest of the conflicts.. I don't know where those may have come in.

If at any time you added another repository (say atrpms) to your yum configuration, and didn't disable those when you issued update that maybe the cause.

But to be clear for others that read this:

You should not enable updates-testing and then do a yum update [all].. You should only be looking to get myth from updates-testing and not the other kernels, etc.

And for general updating this would be preferred:

yum --disablerepo=* --enablerepo=fedora,updates,rpmfusion-free,rpmfusion-free-updates,rpmfusion-nonfree,rpmfusion-nonfree-updates update

So that it doesn't pull in from any other repos that may have been added (if any were).

Ryan

»

Ryan, From your post on

Submitted by Shredder on October 23, 2009 - 12:21pm.

Ryan,

From your post on the main page about upgrading to .22, what should be done differently for those of us that run a separate BE and FE?

I am not near my machine to see if I have the mythfrontend on my backend (I set it up as a back-end only during installation). I would assume we update the BE as per your instructions then do the same with the FE and then run the frontend to upgrade the database?

Thanks for the help,
Shredder

»

Actually.. If you launch the

Submitted by pisani on October 23, 2009 - 12:23pm.

Actually.. If you launch the frontend from anywhere (provided the DB access is available). It should upgrade the schema. I upgraded my backend schema from frontend in the livingroom.

Oh.. alternatively you can launch mythtv-setup and it'll upgrade the schema as well...

Ryan

»

Sweet. Thanks for the quick

Submitted by Shredder on October 23, 2009 - 1:24pm.

Sweet. Thanks for the quick response. Hopefully I can try this out this weekend.

Shredder

»

I just might get flamed for this...

Submitted by n00bdora on October 19, 2009 - 12:48pm.

I have been using MythTV for about 5 years now, intially via Fedora 3 (Thx Jarod) and then via MythDora (a very streamlined process to setup but gets outdated quickly due to 6 month release cycle of Fedora). Based on what I have read so far and seen, it makes more sense to part ways from Fedora and use a more LTS such as CentOS (CentTV anyone?).

~~~~~~~~~~~~~~~~~~
Mythdora v10.21 64-bit (MythTV v0.21-21) as of 9/13/2009.
N00b to Linux and MythDora. Prior minimal MythTV experience.

—

~~~~~~~~~~~~~~~~~~
Downgraded to MythDora v10.22 x64 (seamless integration of external media player, subtitles from external srt/sub files are more important to me).

»

You won't get any buy on

Submitted by pisani on October 19, 2009 - 2:23pm.

You won't get any buy in from me. The problem with CentOS is that the kernel base is way old, and hardware support is often not up to snuff because of it.

I update my systems fairly regularly.. but I really only do it when I need to fix something. For my mythtv hosts, I only keep them updated enough to do what I want. So the idea of a long term distro means very little to me.

What exactly are you updating or what's the purpose of your updating exactly?

Ryan

»

No flaming. But I agree with

Submitted by hball01 on October 20, 2009 - 9:40am.

No flaming. But I agree with Ryan and support Fedora. You get newer hardware support and newer functionality faster. This allows me to upgrade to the newer cooler hardware faster when I want. If a system doesn't need an upgrade, it continues to run fine.
Recent fedora releases seem to be stable enough to just download MythTv from "RPM fusion test" and run stable. I have a BE:FE:mythweb setup on Fedora 11 and MythTV 22 RC1 running on a 64 bit test system. I just had to do one minor tewak to /etc/httpd/conf.d/mythweb.conf to get all working; I'm looking forward to the upgrade procedure/download to migrate my main system. By the way, mythdora team, good work. It's appreciated.

»

or will it be better to wait

Submitted by RXM307 on October 18, 2009 - 6:59pm.

or will it be better to wait for Mythdora 11.22?

»