FS#73595 - [uwsgi-plugin-python] PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Attached to Project:
Community Packages
Opened by HLFH (HLFH) - Wednesday, 02 February 2022, 10:30 GMT
Last edited by David Runge (dvzrv) - Friday, 04 February 2022, 00:31 GMT
Opened by HLFH (HLFH) - Wednesday, 02 February 2022, 10:30 GMT
Last edited by David Runge (dvzrv) - Friday, 04 February 2022, 00:31 GMT
|
Details
Description:
Hi, The package uwsgi on the official stable repository [community] needs a Python 3.10 patch since at least early November. There is not yet a 2.0.21 release for uwsgi despite my ask to the upstream uwsgi devs. But this patch is available upstream: https://github.com/unbit/uwsgi/pull/2363. As the project searxng (https://github.com/searxng/searxng) required a working version of uwsgi on ArchLinux (https://aur.archlinux.org/packages/searxng-git/), I had to quickly create a fork uwsgi-ng which includes the Python 3.10 patch: https://aur.archlinux.org/packages/uwsgi-ng/. Because otherwise, searxng package on the AUR would be broken for too long. But Fabio Lolix AUR user tried to delete my package. He succeeded once (not the second time), and my trust towards how AUR is handled was reduced: because of the first deletion, my package searxng-git was (again) broken with the failing uwsgi dependency. I was surprised the [community] uwsgi maintainers did not know about this Python 3.10 issue. I did not communicate well with them, since my trust was no more there. Additionally, a lot of python-* packages are not very much maintained on [community] or on the AUR. And we need to do something about that. Can you please integrate the patch onto your community version: https://aur.archlinux.org/cgit/aur.git/tree/uwsgi-2.0.20-python3.10.patch?h=uwsgi-ng You can see my PKGBUILD here to see how I handled this patch: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=uwsgi-ng Additional info: * package version(s): 2.0.20 uwsgi release on [community] needs a Python 3.10 patch * config and/or log files etc: no need * link to upstream bug report: https://github.com/unbit/uwsgi/pull/2363 Steps to reproduce: searxng python project is an example > https://github.com/searxng/searxng/issues/662#issuecomment-1002021671 |
This task depends upon
Closed by David Runge (dvzrv)
Friday, 04 February 2022, 00:31 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with uwsg-plugin-python 2.0.20-6
Friday, 04 February 2022, 00:31 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed with uwsg-plugin-python 2.0.20-6
> The package uwsgi on the official stable repository [community] needs a Python 3.10 patch since at least early November.
Yet you only report this *now*.
> As the project searxng (https://github.com/searxng/searxng) required a working version of uwsgi on ArchLinux (https://aur.archlinux.org/packages/searxng-git/), I had to quickly create a fork uwsgi-ng which includes the Python 3.10 patch: https://aur.archlinux.org/packages/uwsgi-ng/.
No, you did not have to do any of that. What you should have done is read the AUR submission guidelines (https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission), which you clearly violated by uploading the package.
Instead of reporting a bug (https://wiki.archlinux.org/title/Bug_reporting_guidelines) you have flagged the package out of date and repeatedly written to us, without stating any details as to what exactly is broken in what way (even after asking you to do so).
Creating a new package in the AUR to apply a single patch does not really help anyone and unfortunately comes across as rather selfish in this case :-/
Arch Linux is a community effort and as such relies on people participating and reporting bugs. Creating a "fork" just to fix your own use-case has unfortunately no benefit to the larger community.
Instead of enabling us to fix the issue for everyone, you prevented that for months. Please make sure to create a bug report right away the next time!
I will fix this issue in an upcoming pkgrel bump.