Comment 3 for bug 1630824

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.