Quoting Alexandre Rossi (2019-10-17 13:33:20) > > > > >Do you require some assistance regarding a new upload of uwsgi? > > > > >I'm eager to dedicate some time to it if you can't do so. :) > > > > > > > > I have a patch but I have not been able to test it yet because > > > > the py2 removal makes the package FTBS... I'm close to fix it > > > > though. I'll post an update here by wednesday. > > > > > > The patch I want to test is here: > > > https://sml.zincube.net/~niol/repositories.git/uwsgi/commit/?id=5e0246cc5d27ea2ccd29e938ceb24913431da364 > > > > > > Unfortunately it does not build (which is not related to the > > > patch): > > > > > > plugins/gevent/../python/uwsgi_python.h:2:10: fatal error: > > > Python.h: No such file or directory <Python.h> > > > > > > If I try to remove even more py2, I'm stuck with: > > > > > > *** uWSGI building and linking plugin plugins/asyncio_python3 *** > > > Error: unable to find directory 'plugins/asyncio_python3' > > > > > > Which means I've messed up debian/rules because it should try to > > > build plugins/asyncio and not plugins/asyncio_python3 . I need to > > > find more time to understand how this works with plugins flavours, > > > stems, etc. I also did not find yet some kind of cdbs debug mode > > > (like DH_VERBOSE=1). > > > > What happened to "It should be as simple as not building the > > matheval plugin"? > > The no-py2 patch[1] in the salsa repository breaks the build. > > [1] > https://salsa.debian.org/uwsgi-team/uwsgi/commit/fdf4e8cadeabf6bbad38b63661a0275d7264a5c8 > > > Please do *NOT* upload a custom fork of > > uwsgi-converted-to-Python3!!! > > > > If you want to help convert uwsgi to Python3, then please work > > directly upstream on that. This Debian package should *not* become > > a fork of the upstream project. > > I'm not doing that.
Phew :-) > I think I did not explain well what was my problem. So I'll try to > rephrase. > > 1) I drafted a patch to fix #941432 (see above) > 2) I tried to build uwsgi using the latest salsa code (master branch) with it. > I found out that the current code does not build. > 3) I tried to fix this failure to build related to py2 removal but I'm > currently stuck with the errors described above. debian/rules needs > fixing. I need to find time to investigate further. Thanks for the clariication - and sorry that I totally misunderstood your previous post: I am to blame for not properly reading your email! I now reverted that broken commit - please try again from a known working state of the package. Sorry for the trouble! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature