Thanks for the info Gary. However, I have not found any documentation, bug reports, issues, etc regarding the issue you have described. https://src.fedoraproject.org/rpms/python-mysql https://src.fedoraproject.org/rpms/python-mysqlclient
Both the python-mysql and python-mysqlclient packages point to the same upstream github site: https://github.com/PyMySQL/mysqlclient Could it be the issue you described is no longer relevant or was resolved some time ago? If there were evidence for the issue, I would be glad to look into it, but at the moment it seems like I am chasing a ghost. Thanks, Andy No Trees were killed in the sending of this message. However, a large number of electrons were terribly inconvenienced. ________________________________ From: Gary Buhrmaster <[email protected]> Sent: Tuesday, July 26, 2022 11:00 AM To: Andrew Bauer <[email protected]> Cc: RPM Fusion developers discussion list <[email protected]> Subject: Re: Mythtv and mythweb el9 branch request On Tue, Jul 26, 2022 at 3:27 PM Andrew Bauer <[email protected]> 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.
_______________________________________________ rpmfusion-developers mailing list -- [email protected] To unsubscribe send an email to [email protected]
