[mythtv-users] Upgrade path to Ubuntu 16.04

Mike Perkins mikep at randomtraveller.org.uk
Sat Jan 7 11:13:05 UTC 2017


On 07/01/17 08:10, Johan Van der Kolk wrote:
>
>> On 06 Jan 2017, at 01:17, Anthony Giggins <seven at seven.dorksville.net> wrote:
>>
>>
>>
>> On 6 January 2017 at 10:07, Stephen Worthington <stephen_agent at jsw.gen.nz <mailto:stephen_agent at jsw.gen.nz>> wrote:
>> On Thu, 5 Jan 2017 21:03:18 +0100, you wrote:
>>
>>>
>>> Hello,
>>>
>>> while I am planning to move my backend to a new server, I stumbled across the fact that 0.27/fixes which I’m running now won’t run on Ubuntu 16.04.
>>> This due to a Qt version bump. And I need 0.28 to put on my new server if I want to move to 16.04.
>>>
>>> What is the best upgrade path, considering that I want my slave BE to stay on 14.04 for the time being?  (the DVB drivers are creating issues with every kernel upgrade, so I rather leave that system on 14.04 until I have certainty that the drivers work fine again)
>>>
>>> Johan
>>
>> You can upgrade to 0.28 and 0.28/fixes on 14.04, and it is best to do
>> that before upgrading to 16.04.  There should be no problem with
>> mixing 14.04 and 16.04 systems as long as they all use the same MythTV
>> version.
>>
>> Yep I second this, my backend is still 14.04 but all my frontends are now 16.04 all running 0.28/fixes.
>>
> Ended up with around 50 encoders with the MBE thinks are on the SBE, but when running setup on the SBE it just showed the normal old ones. Something went wrong here. Dunno what yet, but the SBE does not like them, and fails them all.
>
Is there a possibility that the two BEs are talking to different databases?

Also, if you have "50 encoders" that implies that you haven't done a "Delete ALL tuners" operation 
first (not "Delete all tuners on <host>). Do that and it should clear out the crud.

-- 

Mike Perkins



More information about the mythtv-users mailing list