Releases retrieved: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11, 0.0.12, 0.0.13, 0.0.14, 0.0.15, 0.0.16, 0.0.17, 0.0.19, 0.0.20, 0.0.21, 0.0.22, 0.1.0, 0.1.1 Upstream release that is considered latest: 0.1.1 Current version/release in rawhide: 0.0.20-12.fc37 URL: https://pypi.org/project/aiomysql/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/265875/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/python-aiomysql
This update is needed urgently, as the current package fails to import in Rawhide with PyMySQL 1.x: File "/usr/lib/python3.11/site-packages/aiomysql/connection.py", line 19, in <module> from pymysql.util import byte2int, int2byte ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ModuleNotFoundError: No module named 'pymysql.util'
Can you please try to take a look at this? The package is not usable. Thanks!
Polite ping… I have an FTBFS bug in python-databases for which this is the fix…
https://src.fedoraproject.org/rpms/python-aiomysql/pull-request/1
In addition to the pings and NEEDINFO in this issue, I tried sending Fabian a direct email on 2022-18-15. I want to resolve bug 2105063, but I don’t want to start the nonresponsive maintainer process here while bug 2117916 is in progress. @mhroncok, would you consider reviewing the linked PR and possibly merging to Rawhide and F37 as a provenpackager?
I can, but could you please go trough with https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ as well?
(In reply to Miro Hrončok from comment #6) > I can, but could you please go trough with > https://docs.fedoraproject.org/en-US/fesco/ > Policy_for_nonresponsive_package_maintainers/ as well? I think I would like to see if I learn anything from doing the same process for ignatenkobrain[1][2], since they are a similar and somewhat unusual case: a very prolific packager who has added dozens or hundreds of packages to the distribution and is still active in Fedora, including updating packages, but at the same time seems to be almost impossible to contact in practice. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2117916 [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TLEFFRPSAX2U2Q2SYO52RWKMUJC47QI6/
To be honest I don't see why this was not resolved weeks ago as all commenters here are members of @python-sig (or nowadays @python-packagers-sig) or even provenpackager.
The @python-sig/@python-packagers-sig group has no privileges on https://src.fedoraproject.org/rpms/python-aiomysql.
FEDORA-2022-0c8d936b97 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c8d936b97
FEDORA-2022-0c8d936b97 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.