Hi,
we see autopkgtest failures of uwsgi-plugin-ruby with our recent uploads of Ruby 3.3 and others.
This report is confusing because all is well in unstable. Not so in testing.
So I tried to build the package and run autopkgtest myself. The first error that comes up is:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/src/uwsgi/t/../uwsgi'
It seems this is running in a mix of uwsgi-plugin-ruby 0.0.2 andi
uwsgi <= 2.0.28-2 .
It is looking for the binary in /usr/src instead of /usr/bin in /usr/src/uwsgi/t/runner. After patching that, the next errors was:
FileNotFoundError: [Errno 2] No such file or directory: 'javac'
jwsgi plugin tests should not run for src:uwsgi-plugin-ruby.
So, it seems that JDK is missing as a dependency. But even after installing that, I still see errors, like e.g.:
Eopen("/usr/lib/uwsgi/plugins/psgi_plugin.so"): No such file or directory [core/utils.c line 3709]
!!! UNABLE to load uWSGI plugin: /usr/lib/uwsgi/plugins/psgi_plugin.so: cannot
open shared object file: No such file or directory !!!
/usr/bin/uwsgi: unrecognized option '--psgi' getopt_long() error
Same for psgi.
I don't believe that the package is currently passing autopkgtests if run due to the issues mentioned above, so I cannot debug further if there really is an
issue with Ruby 3.3. Please check it out and adjust the severity as you see fit.
There is no issue with ruby 3.3, this is an issue with both src:uwsgi and src:uwsgi-plugin-ruby providing ruby plugin binaries currently in testing.
This should settle down once src:uwsgi > 2.0.28-2 migrates.
Thanks for reporting,
Alex
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)