[mythtv-users] RPMFusion 0.27 availability

[Gary Buhrmaster]

On Tue, Oct 22, 2013 at 4:13 PM, Dave Ulrick <d-ulrick at comcast.net> wrote:
...
> How will the database schema upgrade happen when the 0.27 RPMFusion RPMs are
> installed? Will it happen automatically the first time the 0.27 mythbackend
> or mythfrontend is started?

Well, yes, or no.  And that is one of the possible issues.  By default
if a (newer version) backend is started if will prompt (if possible) for
the upgrade (not viable, obviously, if started via a system startup
script).  Otherwise it waits for awhile (30 seconds?), and then tries
to get the lock to start the upgrade.  If the lock works, the BE will
try to backup the database, and then the upgrade happens (one
hopes successfully), and then things go on.  Errors may stop the
process, and because it happened "auto-magically" one might end
up dazed and confused(*) wondering what is going on.  Also, because
some DB upgrades can take a long time, some people reboot in the
middle, causing database issues which require one to restore to the
last backup.  Probably 80%(**) of the time everything works perfectly.
You might be in that magic 20% though.

I believe the "recommended" solution is to stop all BE/FEs, take a
database backup (you can never have too many), run the database
optimize script to insure that there are no crashed tables or other
problems, take another database backup (especially if optimize
fixed anything), upgrade to the newer MythTV binaries/libraries,
run mythtv-setup to manually upgrade, wait, wait, wait until it is done,
run another database backup, and start the BE.

Personally, I would suggest excluding MythTV from yum until
you are ready to be able to take the time to do it right, and check
the results.

Gary

(*) The Linux ECC module reports being dazed and confused.

(**) Random numbers thrown into the argument to appear to
be more valid or official.