[mythtv-users] Upgrade to 0.27

[Michael T. Dean]

On 11/14/2013 04:54 PM, Gary Buhrmaster wrote:
> On Thu, Nov 14, 2013 at 9:27 PM, Eric Sharkey wrote:
> ...
>> Most end users will be relying on packagers' scripts to handle this.
> And that *can* end up being a badness.
>
>> apt-get dist-upgrade, then everything is already up, running, and at
>> least the backend part of the database schema is already done.
> Except, of course, if the database upgrade fails, and then those
> same users may have no idea why their backend is not starting,
> and cannot start.

And if the database backup failed before the failed database upgrade, 
and if the user (or the packager scripts) didn't do a manual backup 
before starting mythbackend (or if the packager scripts did one and the 
user can't find it or doesn't know it exists), the user may have a 
really broken system (and even one that--after they hammer on it and 
"force" the upgrade to work using the database whose integrity is 
indeterminate due to the failed upgrade attempt (and not knowing exactly 
when the failure occurred)--may have corrupt data that doesn't result in 
problems immediately--possibly causing problems in days/months or even 
at next upgrade).

Eventually I may split out the DB upgrade into a separate program that 
packaging scripts can run at the command-line and receive information 
(such as whether it completed successfully or not) so that they don't do 
things like start mythbackend, which attempts a DB backup and upgrade, 
which fails, which causes mythbackend to shut down, which the (up)start 
script/monitor notices, which causes it to restart mythbackend, which 
attempts a DB backup and upgrade, which fails...  It's not high on my 
list of things to do, though.  It's easy enough for me to just run 
mythtv-setup to upgrade my DB before I run mythbackend after an upgrade.

Mike