On Tue, Jul 26, 2022 at 3:27 PM Andrew Bauer
<zonexpertconsulting(a)outlook.com> wrote:
Thanks for the heads up, Gary.
According to that bug report, there is movement to retire python-mysql and use
python-mysqlclient instead. The latter has already been built for el9. I am currently out
of town for work and will look into how this affects mythtv when I return.
The package naming in fedora for the various
python mysql clients is somewhat different than
some other distros (and upstream), so I have
lost track of which library supports what functionality,
but I seem to recall that the python-mysql package
has an upstream of mysqlclient-python, while
the python-mysqlclient package has an upstream
of mysqlclient. Similar but different.
In order to try to get out of mysql/mariadb confusions
there was an (abortive) attempt to move to the pure
python mysql client a number of years ago now for
MythTV, but at the time the MythTV python bindings
used/depended on some less common feature that
did not work with the different implementation for
some specific thing, and there was some effort put
in by a few devs to create a test harness to identify
the functionality that was different and therefore
broken during runtime with different implementations.
You may wish to work with the project devs to
get that test harness to validate changes to the
support library used to avoid runtime issues
(or work to replace the specific thing that MythTV
was using; or just volunteer to build python-mysql
in epel9).
Good luck.