[mythtv-users] Downgrading to 0.31 on Debian bookworm (debian-multimedia)

[Mike Perkins]

On 31/07/2023 23:29, James wrote:
> 
> 
>> On 1 Aug 2023, at 5:05 am, Ram Ramesh <rramesh2400 at gmail.com> wrote:
>>
>> It appears that when I upgraded my frontend host from Debian bullseye to bookworm, my myth version changed from 0.31 to 0.33. Specifically, before upgrade it was:
>>> MythTV Version : v31.0
>>> MythTV Branch :
>>> Network Protocol : 91
>>> Library API : 31.20200101-1
>>> QT Version : 5.11.3
>> After upgrade it is:
>>> MythTV Version : v33.1-525efb656d6
>>> MythTV Branch : fixes/33
>>> Network Protocol : 91
>>> Library API : 33.20220913-1
>>> QT Version : 5.15.8
>>
>> This happened as I get my mythtv through debian-multimedia.
>>
>> I need to go back to 0.31 as my backend is still 0.31 and I am reluctant to upgrade (the backend) at this time as it serves a couple of 0.31 frontends that I cannot upgrade at this time.
>>
>> Is there anyway I can downgrade to 0.31 and still stay in bookworm? Otherwise, I will have to wipe clean and install bullseye and get myth 0.31. If possible, I would like to avoid this route. Please let me know if I have any solution.
> 
> I have never used repos for my mythtv setup so I can say following:
> the wiki on build from source is quick and easy but you need to have the background skills eg setup the DB eg systemd
> 
The problem with building from source, if you are not a developer, is that it takes time to set that 
build system up the first time and become familiar with it. Then, by the time you come to do the 
next upgrade, you have forgotten how it all works and maybe the system has changed anyway.

For myth, uprgades/updates come sufficiently infrequently that the use of repos such as 
deb-multimedia are adequate for the purpose, even for someone like me who *is* a developer. 'apt 
update; apt upgrade' is quick and easy and keeps myth in step with the rest of the software.

The OP has also said that he has two frontends he cannot yet upgrade; building from source risks 
that, even though he selects the same myth version, something will not be compatible. Using the same 
repo on every myth host ensures that all systems are exactly in lockstep.

-- 

Mike Perkins