<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 1, 2023 at 6:10 PM Mike Perkins <<a href="mailto:mikep@randomtraveller.org.uk">mikep@randomtraveller.org.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 01/08/2023 21:51, Ram Ramesh wrote:<br>
> On 8/1/23 05:35, James Abernathy wrote:<br>
>><br>
>><br>
>> On Tue, Aug 1, 2023 at 4:38 AM Mike Perkins <<a href="mailto:mikep@randomtraveller.org.uk" target="_blank">mikep@randomtraveller.org.uk</a>> wrote:<br>
>><br>
>> On 31/07/2023 23:29, James wrote:<br>
>> ><br>
>> ><br>
>> >> On 1 Aug 2023, at 5:05 am, Ram Ramesh <<a href="mailto:rramesh2400@gmail.com" target="_blank">rramesh2400@gmail.com</a>><br>
>> wrote:<br>
>> >><br>
>> >> It appears that when I upgraded my frontend host from Debian<br>
>> bullseye to bookworm, my myth version changed from 0.31 to 0.33.<br>
>> Specifically, before upgrade it was:<br>
>> >>> MythTV Version : v31.0<br>
>> >>> MythTV Branch :<br>
>> >>> Network Protocol : 91<br>
>> >>> Library API : 31.20200101-1<br>
>> >>> QT Version : 5.11.3<br>
>> >> After upgrade it is:<br>
>> >>> MythTV Version : v33.1-525efb656d6<br>
>> >>> MythTV Branch : fixes/33<br>
>> >>> Network Protocol : 91<br>
>> >>> Library API : 33.20220913-1<br>
>> >>> QT Version : 5.15.8<br>
>> >><br>
>> >> This happened as I get my mythtv through debian-multimedia.<br>
>> >><br>
>> >> I need to go back to 0.31 as my backend is still 0.31 and I am<br>
>> reluctant to upgrade (the backend) at this time as it serves a<br>
>> couple of 0.31 frontends that I cannot upgrade at this time.<br>
>> >><br>
>> >> Is there anyway I can downgrade to 0.31 and still stay in<br>
>> bookworm? Otherwise, I will have to wipe clean and install<br>
>> bullseye and get myth 0.31. If possible, I would like to avoid<br>
>> this route. Please let me know if I have any solution.<br>
>> ><br>
>> > I have never used repos for my mythtv setup so I can say following:<br>
>> > the wiki on build from source is quick and easy but you need to<br>
>> have the background skills eg setup the DB eg systemd<br>
>> ><br>
>> The problem with building from source, if you are not a developer,<br>
>> is that it takes time to set that<br>
>> build system up the first time and become familiar with it. Then,<br>
>> by the time you come to do the<br>
>> next upgrade, you have forgotten how it all works and maybe the<br>
>> system has changed anyway.<br>
>><br>
>> For myth, uprgades/updates come sufficiently infrequently that the<br>
>> use of repos such as<br>
>> deb-multimedia are adequate for the purpose, even for someone like<br>
>> me who *is* a developer. 'apt<br>
>> update; apt upgrade' is quick and easy and keeps myth in step with<br>
>> the rest of the software.<br>
>><br>
>> The OP has also said that he has two frontends he cannot yet<br>
>> upgrade; building from source risks<br>
>> that, even though he selects the same myth version, something will<br>
>> not be compatible. Using the same<br>
>> repo on every myth host ensures that all systems are exactly in<br>
>> lockstep.<br>
>><br>
>> --<br>
>> Mike Perkins<br>
>><br>
>><br>
>> I put together a way to build the packages for Debian 12 for MythTV over on the MythTV Forum.<br>
>><br>
>> <a href="https://forum.mythtv.org/viewtopic.php?f=29&t=5466" rel="noreferrer" target="_blank">https://forum.mythtv.org/viewtopic.php?f=29&t=5466</a> <br>
>> <<a href="https://forum.mythtv.org/viewtopic.php?f=29&t=5466" rel="noreferrer" target="_blank">https://forum.mythtv.org/viewtopic.php?f=29&t=5466</a>><br>
>><br>
>> Jim A<br>
>><br>
>> _______________________________________________<br>
>> mythtv-users mailing list<br>
>> <a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
>> <a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
>> <a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
>> MythTV Forums:<a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
> Jim,<br>
> <br>
> Sorry if this is obvious, but I want to be sure. I thin you are suggesting that I follow your <br>
> link and the steps in it to build 0.31 .deb packages for 31 and install it in bookworm. Is this <br>
> correct? I will give it a try over coming weekend.<br>
> <br>
> Someone suggested pinning myth to 31 before switching from bullseye to bookworm. Do you think <br>
> that will work? I ask because I have a couple of other hosts running 31 in bullseye and eventually I <br>
> will have to upgrade them to bookworm. So, wondering, if there is an easy way out of this upgrade <br>
> issue. Of course, moving to myth 33 is the right move, but prefer to wait on that till I know I can <br>
> live with a week of downtime, if things go wrong.<br>
> <br>
If I can offer a word of caution. When I... upgraded? I actually backed everything up, swapped out <br>
the system disks and did a fresh install - that way, if it all went pear-shaped, I could (in theory) <br>
just put the old disks back and think again.<br>
<br>
Going from bullseye to bookworm I /did/ actually follow the Debian upgrade instructions for one <br>
non-mythtv host and it was the most frustrating few hours of my life that I'll never get back again. <br>
I'm about to nuke that box and do a fresh install.<br>
<br>
TL;DR: don't upgrade, do fresh installs if you can.<br>
<br>
-- <br>
<br>
Mike Perkins<br></blockquote><div><br></div><div>Starting fresh with a new ssd is what I always do. Now that 1TB m2.NVME SSDs are sub $50, I keep a stack in my lab.</div><div><br></div><div>Jim A</div><div> <br></div></div></div>