<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">> > I knew this day was coming... My trusty Myth box, nearly 8 years old,<br>
> ><br>
</div><div class="">> > Anyone with experience upgrading from a way-old Myth?<br>
><br>
> Just do an iterative upgrade... 0.23, 0.25, 0.27.... should be pretty<br>
> flawless as far as upgrading the critical data (recording history). Then<br>
> I would do a full DB backup (just in case) and a partial DB backup (for<br>
> restoring to the new system).<br>
<br>
</div>Dang, forgot to mention one (critical) part: the old box is running Fedora<br>
9 (pre-Core days) with a /boot too small to upgrade, or I would have way<br>
back. And could I even get RPMs for 0.23 for it?<br>
<br>
So what I'd have to do is install Fedora-something on the new machine and<br>
do the Backup/Restore to it, and then continue upgrading Myth on it.<br></blockquote><div><br></div><div>You don't necessarily need to upgrade Fedora to update myth (you may need to build from source, and you may have dependency issues though).</div>
<div><br></div><div>You could probably get away with creating a VM on another system, installing a linux distro of your choice that included Mythtv 0.21, then upgrading from there... just to get the schema where it should be.</div>
<div><br></div><div>Its a shame that no one developed the schema updater as a separate app that would update any version to any other version... would be handy.<br></div></div></div></div>