On 26 août 2025 08:35, Ram Ramesh <rramesh2400@???> wrote:
> I am with debian bookworm, but kept deb-multimedia at bullseye when I
> upgraded to bookworm as I did not want mythtv version to change. Now
> stable will be switching from bookworm to trixie. Also mythtv has moved
> to v35 or may be v36.
Version in this repo are:
,----
| mythtv-dmo | 31 | bullseye
| mythtv-dmo | 33 | bullseye-backports
| mythtv-dmo | 33 | bookworm
| mythtv-dmo | 35 | bookworm-backports
| mythtv-dmo | 35 | trixie
`----
> I feel left behind, but very afraid to upgrade as in the past every
> upgrade had landed me in misery as something or other broke. I am
> wondering if anyone upgraded from 0.31 to any one of 0.32-0.35 under
> debian bookworm from deb-multimedia? If so, what are the steps you took
> to upgrade.
From upstream v35 release notes
,----
| Data Migration: v35 will only support direct upgrades from v29 or higher.
`----
https://www.mythtv.org/wiki/Release_Notes_-_35
> I have one host that is both front and backend. This is the only
> backend. There are two other frontends on my home network. I use HDHR
> network tuners with dnsmasq assigning static IP using their ethernet
> address as the key. I also upgraded mythfilldatabase to use the newer
> method to grab schedules (is that called json method?)
>
> I want to upgrade front+back end host first. Here is what I plan to do
>
> 1) Make sure bookworm is upto date.
> 2) stop mythtv front and backend. Stop backend service so that it does
> not fire on reboot.
> 3) Change sources.list to proper bookworm deb-multimedia entries
> 4) apt update and apt upgrade
> 5) Reboot to make sure that everything is alive
> 6) run mythtv-setup which probably will do a database upgrade
> 7) start mythtv backend service
> 8) start frontend and check. If everything is ok, repeat steps 3-4 and 8
> on other frontends.
Seems to be good for me.
