On 2023-01-15 12:25:36 (+0100), David Runge wrote:
There has been a problem  introduced by not renaming the soname of libphp-legacy.so. The soname was still libphp.so, so linking against libphp-legacy.so led to dependents requiring libphp.so instead (this was also the case for the apache plugin btw). This should have been tested more thoroughly and it took me some time to figure out what was going wrong yesterday. A patched php-legacy is in [testing] though.
Meanwhile, there still seem to be issues with uwsgi-plugin-php-legacy and it would be great, if you could help solve them, since this is broken after switching to php-legacy.
I would really appreciate if there was feedback on this issue from your side.
The move to stable was (as you mentioned yourself) a potential breaking change. Doing this on a Friday and then not being available to fix potential breakage is not cool. Currently everyone relying on uwsgi + php-legacy is affected by this.