uWSGI Ubuntu package

uwsgi-plugin-psgi dropped the useful "coroae" option in Xenial; it should go back in Yakkety

Bug #1630824 reported by Jamie Lokier
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
uWSGI Ubuntu package
New
Undecided
Unassigned

Bug Description

I presume the "--coroae" option was dropped in Xenial because the libcoro-perl package failed to build. (Documentation of the option is here: http://uwsgi-docs.readthedocs.io/en/latest/PSGIquickstart.html ). There is a backport request to restore libcoro-perl in Xenial, with a working patch from Debian, but nothing else has happened there.

However libcoro-perl is restored in Yakkety, so the "coroae" option in uWSGI should be restored as well.

Or perhaps it should be in a separate subpackage of its own: uwsgi-plugin-coroae, as Fedora does.

As far as I know this is the only scalable way to do event-driven code with uWSGI Perl applications, and therefore pretty much essential for doing things like Websockets and long-polling with uWSGI and Perl.

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

I reported this problem 3 months ago. and haven't had any response.

I don't want to make a fuss, but does anyone read these reports and is it worth reporting them? Should they be reported to Debian instead (even though I'm not using Debian?)

I imagine the fix is quite simple for whoever removed the coroae option in the first place - just revert that change.

Thanks.

Revision history for this message
Anton Petrusevich (apetr) wrote :

I reported this bug to Debian package maintainers <email address hidden>, <email address hidden>, <email address hidden>, <email address hidden> in December 2017 and then one more time in February 2018 and also without any response or reaction.

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

I see no reason why the uWSGI package cannot simply re-enable "coroae_plugin.so".

The single reason "coroae_plugin.so" was disabled in the uWSGI build was temporary, and it was fixed and released 3 years ago, so I don't see any reason not to re-enable the plugin. For some applications it's an essential part of uWSGI functionality. And because it's a plugin, enabling it shouldn't break anything else.

Thanks Anton. I'm surprised nobody replied to either report, because there are other uWSGI updates in the changelog. It's hard to tell what the problem is if nobody responds.

So, I've just installed Ubuntu Server 19.04.

Everything I need is packaged, even NginX is looking up to date :-), except I still can't use the uWSGI package.

So I have to build uWSGI from upstream source. It's actually not much of a burden, but it means no regular security updates as with other packages, which is unfortunate.

(I also have to build and dispatch distro-version-specific binaries in my webapps tree, because uWSGI depends on libperl.so which is distro-version-specific.)

I can live with the workaround, but it seems silly to keep the plugin disabled still.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.