Debian Patches

Status for rsyslog/8.2510.0-5

Patch Description Author Forwarded Bugs Origin Last update
Don-t-create-a-database.patch Don't create a database
dbconfig-common, which is used by rsyslog-mysql and rsyslog-pgsql, takes
care of creating the database for us.		 Michael Biebl <biebl@debian.org> no 2014-03-13
Increase-timeouts-in-imfile-basic-2GB-file-and-imfile-tru.patch Increase timeouts in imfile-basic-2GB-file and imfile-truncate-2GB-file

Those tests can take a long time, especially on slow architectures like
armhf, so bump the test timeouts considerably.		 Michael Biebl <biebl@debian.org> no 2020-02-28
doc-make-git-optional-for-Sphinx-builds-dist-tarballs.patch doc: make git optional for Sphinx builds (dist tarballs)
Building documentation from the dist tarball failed with a RuntimeError
("git executable not found") thrown during Sphinx startup. The helper
module hard-required git even when no .git repo is present.

This change replaces the hard requirement with a safe wrapper that
returns placeholders when git or a repository is unavailable. This lets
Sphinx complete when building from release/dist sources, while keeping
dev builds unchanged.

Details:
- conf_helpers.py: introduce _run_git(); return 'unknown'/'nogit' for
branch/commit and '0.0' for tag-derived versions when git is absent.
- Harden next-version parsing for non-git environments.
- conf.py already guards dev-only dynamic strings behind .git presence.


(cherry picked from commit 18c8eed4858c4fb5f04018dd8b12148822129069)		 Andre Lorbach <alorbach@adiscon.com> no 2025-10-20
doc-enable-parallel-Sphinx-builds-silence-edit_on_github.patch doc: enable parallel Sphinx builds; silence edit_on_github
Mark the custom edit_on_github extension as safe for parallel
reading/writing and forward GNU make's -j to sphinx-build. This removes
the Sphinx warning and allows true parallel docs builds.

Changes
- doc/source/_ext/edit_on_github.py: setup() now returns
parallel_read_safe=True and parallel_write_safe=True (plus version).
- doc/Makefile: if SPHINXOPTS lacks -j, propagate -jN from MAKEFLAGS to
sphinx-build. Bare "-j" maps to "-j auto". Respects explicit -j in
SPHINXOPTS.


(cherry picked from commit 81eabd3cb3e358bffcb2e648fcd0102e62660547)		 Cursor Agent <cursoragent@cursor.com> no 2025-10-20
doc-vendor-mermaid-assets-and-fix-offline-viewing.patch doc: vendor mermaid assets and fix offline viewing
Add vendored copies of Mermaid, layout-elk, and D3 JavaScript assets
under doc/source/_static to make documentation builds self-contained
and compliant with packaging policies that forbid CDN dependencies.

Changes:
- Add vendored JavaScript files for Mermaid (11.2.0), layout-elk (0.1.4),
and D3 (7.9.0) under doc/source/_static/vendor
- Force sphinxcontrib-mermaid to use vendored assets via configuration
overrides and install_js monkey-patching
- Create tools/fix-mermaid-offline.py script to convert ES module syntax
to regular script tags for offline compatibility with file:// URLs
- Update doc/Makefile to automatically run the offline fix after builds
- Switch zoom helper bindings to const for modern JavaScript consistency
- Add .codespellignore to skip minified JavaScript files in vendor
directory and exclude common minified JS tokens from spell checking

The documentation now works seamlessly both offline (file:// URLs) and
online (http:// URLs). Basic Mermaid diagrams render correctly in both
cases. ELK layout functionality remains unavailable in offline mode due
to browser CORS restrictions on ES modules.

This resolves CORS errors that occurred when opening HTML files directly
in a browser, eliminating the need to serve files via a local HTTP server.

(cherry picked from commit 83bb383529ad4b66d82916136d6c123f6a657950)		 Andre Lorbach <alorbach@adiscon.com> no 2025-10-22
Skip-potentially-buggy-imrelp-tls-cfgcmd.sh.patch Skip potentially buggy imrelp-tls-cfgcmd.sh
Test imrelp-tls-cfgcmd.sh seems to fail but still report success, which
can create a false impression.

Suspected root cause is in librelp. It may also be that the test
actually succeeds, where it just looks like it failed because of abort
of tcpflood testing tool (due to librelp bug).

The whole point of the test is that an error is generated, and this may
very well happen. And only tcpflood aborts because of the librelp bug.
Core file detection than jumps in, and invalidly treats the tcpflood
core file as a test failure.

While this is investigated, the test will be skipped. Highly like that
this needs to be forwarded either to librelp or is a native tcpflood
bug.

Thanks to Chris Hofstaedtler for reporting the bug and Michael Biebl for
forwarding it upstream.

see also: https://github.com/rsyslog/rsyslog/issues/6267

(cherry picked from commit 70cefe02b5dc96e99514327a9365f99940b51012)		 Rainer Gerhards <rgerhards@adiscon.com> no 2025-11-01
Skip-tests-based-on-omfwd-lb-1target-retry-test_skeleton..patch Skip tests based on omfwd-lb-1target-retry-test_skeleton.sh and omfwd-lb-1target-retry-test_skeleton-TargetFail.sh

Those tests appear to be flaky and fail rather often on
reproducible-builds.org, especially on arm64.

See https://github.com/rsyslog/rsyslog/issues/6308		 Michael Biebl <biebl@debian.org> no 2025-11-19
Skip-imfile-logrotate-async.sh.patch Skip imfile-logrotate-async.sh
This test appears to be flaky and fails rather often on
reproducible-builds.org.

See https://github.com/rsyslog/rsyslog/issues/6293		 Michael Biebl <biebl@debian.org> no 2025-11-23

All known versions for source package 'rsyslog'

Links