[mythtv-users] upgrading from mythbuntu 14.04/0.27 to 0.28 vs. mythbuntu 16.04 install

[John Finlay]

On 11/28/2016 04:04 AM, Jim Abernathy wrote:
>
> On 11/26/2016 06:50 PM, Mark Cooke wrote:
>> Hi Jim,
>>
>> I did a 0.24 to 0.28 recently as a database backup, fresh install to new
>> hardware, and a final restore.
>>
>> My storage configuration didn't change so the NFS mounts on the backend
>> servers were identical.
>>
>>
>> The basic process I followed was the backend migration from
>> https://www.mythtv.org/wiki/Backend_migration and it worked pretty well,
>> so my thanks to everyone that helped put that together.
>>
>>
>> Things that caught me but were very minor:
>>
>> - Channel ID numbers changed on the new system (TBS6205) as compared to
>> the old (Hauppauge dual SD tuner, and a Nova HD USB tuner), so
>> recordings made via the Nova appeared as #1234# instead of using the
>> channel name.  This I fixed by editing the database and updating the old
>> tags to match the new channel IDs and this was mostly a case of changing
>> 2xxx to 1xxx.
>>
>>
>> - Existing cutlists were lost.  I didn't manage to resolve this, but it
>> was not important.[*]
>>
>> So for me, it was relatively painless.  The Mac 0.28 frontend seems to
>> be a bit more glitchy on video playback and quite annoying in sports
>> programmes, but I think that's 0.28 stressing out my 2011 mac mini's
>> capabilities more than 0.24 did.
>>
>>
>> Hope that helps, and Good Luck!
>>
>> Mark
>>
>> [*] For anyone that does care - the cutlists appear to still be there,
>> but going into the recording starts from the very beginning, and trying
>> to edit brings up a blank cut list editor.  I think this is related to
>> the direct database editing I did for the channel number issue that goes
>> something out of step in the database.
> At this point, I backed up my database and went into mcc and changed the
> repository to 0.28.  Then I did a sudo apt-get update, then sudo apt-get
> upgrade, then sudo apt-get dist-upgrade, and finally an sudo apt-get
> autoremove.
>
> Everything worked and the backend worked on reboot, but mythtv-setup
> would not work and mythfrontend would not work local or remote.  I found
> that for remote frontends, I had to go back into MCC and set the mySQL
> setting to enable remote frontends.  Somehow the upgrade reset that.
>
> For mythtv-setup, I had correct the password for the database it got
> reset to mythtv, but was correct in /etc/mythtv/config.xml
>
> Once I fixed those, I'm up and running.
>
> Jim A
>
>> On 26/11/2016 22:19, Jim Abernathy wrote:
>>> I have about 500GB of recorded TV on my mythbuntu 14.04 backend on version 0.27 of mythtv. I’m ready to upgrade to 0.28.
>>>
>>> I’m trying to pick the best way.
>>>
>>> I know I can use MCC and change the repository from 0.27 to 0.28 and do an upgrade in place (making sure I have a current backup of the database).  I could then do a "do release upgrade" and bring the OS to 16.04.
>>>
>>> Is that better than doing a fresh install of mythbuntu 16.04.1??  I’m worrying about restoring the 0.27 database backup to 0.28 after I install 16.04 from scratch?  I have my recording on 2 separate disk that will not be erased by a fresh install.
>>>
>>> Thoughts on how to do this right?
>>>
>>> Jim A
>>>
>>> _______________________________________________

On Mythbuntu 14.04 I tried to run MCC to change to 0.28 but it failed 
and spit out some error messages in Python. So I removed and reinstalled 
MCC and that seemed to fix the startup problem but I couldn't get MCC to 
update the repositories. The message was: URL Error: Failed to download 
new DB .file.

Is the mythbuntu repo download site down or in MCC broken?

John