Updating ansible to newest is faulty ?

[louvanna]

The distribution install of ansible on Debian-bookworm is below the version required to use the MythTV ansible build tools.

I went directly to the ansible website and followed the instructions to add a ubuntu PPA to my apt configuration.
All went well and now I have the newer version. ( or so I think )

https://docs.ansible.com/ansible/latest ... -on-debian

---- evidence ---
Unpacking ansible (10.7.0-1ppa~jammy) over (7.7.0+dfsg-3+deb12u1) ...
Setting up ansible (10.7.0-1ppa~jammy) ...
Processing triggers for man-db (2.11.2-2) ...
---- end evidence -----

But the query of the version used remains the distribution version the core 2.14.18.
---------- evidence ------
root@rpiRCA:/home/ab/build-mythtv/ansible# ansible --version
ansible [core 2.14.18]
config file = /home/ab/build-mythtv/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
ansible collection location = /usr/share/ansible
executable location = /usr/bin/ansible
python version = 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] (/usr/bin/python3)
jinja version = 3.1.2
libyaml = True
-------- end evidence ------------

What am I doing wrong ? or have missed a step?

Further I would ask if my approach will be successful?
when paralleling the helpful post reference below below.

I have attempted to adapt a post by jfabernathy to fit my needs of fixes/31 instead of 34, to match the rest of my myth devices, 2 BE ( Master & Slave ) and 3 FE, now wanting fourth FE.

[UPDATED]How to build mythtv-light (v34) for RPI OS 64bit Bookworm
viewtopic.php?f=46&t=5530&p=28425&hilit=ansible#p28425

[jfabernathy]

My only comment about your approach is why v31? Or why v34. I'd use nothing less than v35. I know that Debian 12 version of ansible is fine for installing the dependencies for Mythtv, but I've never tested it below v34 and in the last year I've only tested v35 or master.

I have v35 built and running on Debian 12 on x86_64 and arm64.
I have v35 built and running on Archlinux.
I have my production backend running Ubuntu 24.04 with mythtv v35 from the ppa:mythbuntu/35

If you want Mythtv on Debian your can use mythtv-light images already built at
https://drive.google.com/drive/folders/ ... YW2ZNw3Pd3
there are some old images for v31 and v32 and the one I built for v35

You can also use the images at deb-multimedia.org.

If you want to build yourself stick to v35. That is what the developers spent their efforts on and none of those fixes are ported back to v31.

These are all my opinions and as I tell my wife, I'm always right

[bill6502]

Good news, nothing faulty.

Ansible v2.14 is fine. If you want more information, see: https://docs.ansible.com/ansible/latest ... changelogs

You'll see that the Community Package 7 depends on the 2.14 Ansible Core. Which is what you've got. If you need more information about Ansible Core and Community, there are pages that explain why it was done.

[louvanna]

Sorry for the delay, work got in the way of this home project.

@jfabernathy -- v31 vs newer v35
I have five installations already, 2 BE and 3 FE on v31. I did not want to cross some unknown compatibility barrier between v31 to v35 when adding #4 FE. My goal was least effort to adding another device, build one or rebuild 4+1.
Is my lack of compatibility concern warranted ?

@bill6502 ansible 2.14
( from memory of the build complaint ) Then why does the build steps halt complaining that the version of ansible is too old ?

[jfabernathy]

First step in upgrades is to backup your database and your Mythtv Storage Group directories.

A good reference on backups and restores of the database.
https://www.mythtv.org/wiki/Database_Backup_and_Restore

After a successful build of Mythtv V35. You should have all the programs and libraries at the same version. When you reboot mythbackend will start upgrading from v31 to v35.

That should be it for the backend, but you need the frontends to be upgraded to v35 unless they are Kodi or Android Leanfront. They don't care what version the backend is.

What I usually do is have my recordings and database backed up externally and build a fresh system. I do this because I might be updating to a new version of the OS as well. Once I have a completely new and working v35 Mythtv system with no recordings except the test ones I made to test the new backend, I restore the database that I saved and copy back all my recordings with the correct permissions.

The copying of the recordings is the longest part depending on how much data. Since I keep all my recordings on a separate hard drive, The rest of a new build and restore usually takes me under an hour including beer breaks.

One method I like to do if use a cheap NUC, like a $200 N100 with 16 GB of ram and 1TB nvme drive as a new backend and install the OS and build the latest mythtv v35 and get it working. Then copy over the recordings onto the the nvme drive and restore the database, then rename the mythtv hostname to match the new backend.

At this point you have a duplicate system. So you will not miss any recordings while you upgrade you old backend hardware.

My setup is easy to do this way because all my frontends for TVs are FireTV 4k sticks or Google TVs running Leanfront. You can simply change the IP address in the Leanfront setup to look at a different backend. Real easy to do with the remote control.

[bill6502]

@louvanna, I'd copy/paste the command line you use and the output. pastebin.com is a handy site. Please put a link to the paste in your reply.

[white_haired_uncle]

First step in upgrades is to snapshot the BE VM. Making the BE virtual was the best decision I've made with myth. The network config to handle the HDHR (REQUIRES broadcast, which is dumber than) took a little learning, but definitely worth it.[1]

Then shutdown the FE and it up (the FE is diskless - also an excellent choice even with debian-ish clients once you get rid of systemd).

[1] Every now and then I entertain the idea of releasing a BE VM image, probably with some sort of MCP-like configuration tool. Maybe one day when I upgrade the main box to something like modern hardware so I can run a virtual hypervisor). That, or submit a PR that removes the need (but NOT ability) for anything but the main BE to access the DB directly.

[white_haired_uncle]

@bill6502 ansible 2.14
( from memory of the build complaint ) Then why does the build steps halt complaining that the version of ansible is too old ?

I'm not really familiar with ansible, but I did notice a couple things in your post that I would check first for anything.

1) You ran ansible --version as root, but you probably actually run it as a non-root user. Different users could use different versions of ansible.

2) related to above, you just ran "ansible" (no path specified). What exactly is it running (`which ansible`, `alternatives --list`, etc)?