Debian Patches

Status for zaqar/23.0.0-4

Patch Description Author Forwarded Bugs Origin Last update
finished-fixing-upstream-tests.patch Finished fixing upstream tests Patch from upstream wasn't enough.

===================================================================
Thomas Goirand <zigo@debian.org> no 2022-09-19
package-all-files.patch no
add-wsgi-application-module.patch Add wsgi application module Thomas Goirand <zigo@debian.org> no 2026-06-02
CVE-2026-107363_OSSA-2026-043_Prohibit_arbitrary_project-id_for_websocket_protocol_access.patch Prohibit arbitrary project-id for websocket protocol access
diff --git a/releasenotes/notes/bug-2161402-f0b9d2052c12b958.yaml b/releasenotes/notes/bug-2161402-f0b9d2052c12b958.yaml
new file mode 100644
index 0000000..e2e8188
Takashi Kajinami <kajinamit@oss.nttdata.com> yes debian upstream https://review.opendev.org/c/zaqar/+/1009251 2026-10-07
zaqar-uwsgi-pyargv-logfile.patch Honor sys.argv when parsing the config in the WSGI entry point uwsgi daemons cannot take --log-file on their own command line, and
openstack-pkg-tools (>= 153) passes --log-file to the WSGI application
through uwsgi's --pyargv. zaqar's WSGI entry point ignored sys.argv
(hardcoded empty argv), so oslo.log, with only log_dir set, derived the
log filename from the bottom-most Python stack frame, which under uwsgi
is the frozen importlib machinery: the API logs into
/var/log/zaqar/<frozen importlib._bootstrap>.log.
.
Pass sys.argv[1:] to CONF() so that --pyargv is honored, and oslo.log
writes to the log file the init script chose.

===================================================================
Thomas Goirand <zigo@debian.org> yes 2026-10-16

All known versions for source package 'zaqar'

Links