Debian Patches

Status for rsyslog/8.2602.0-1

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
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
Fix-doc-version-for-sphinx-build.patch Fix doc version for sphinx-build Michael Biebl <biebl@debian.org> yes upstream 2026-02-21
imfile-preserve-symlink-cleanup-notifications-with-deferr.patch imfile: preserve symlink cleanup notifications with deferred destroy
Why:
The inode-generation refactor moved detect_updates() to deferred destruction in
order to avoid freeing the current active object while the active-list walker is
still using it. That change fixed a real iterator-lifetime problem, but it also
changed the ordering of symlink cleanup in a subtle way.

Impact:
Deleted or replaced symlink targets and their helper directory watches are now
cleaned up in the same update cycle again, including in the
imfile-symlink-ext-tmp-dir-tree scenario.

Before/After:
Before, deferred destruction could postpone the symlink parent rescan until the
graph context needed to discover it was already gone. After this change, the
rescan target is captured before unlink and served safely from the deferred
destroy queue.

Technical Overview:
The symlink teardown path in detect_updates() used to rely on act_obj_destroy()
for a side effect: scan the still-linked active set, find the symlink target via
source_name, and rescan the target's parent tree so that helper watches created
by process_symlink() can be retired.

That assumption stopped being valid once destruction became deferred. By the
time act_obj_destroy() ran, the symlink object had already been detached from the
active list, so the cleanup notification no longer happened at the right point
in the update cycle.

Fix this by making the dependency explicit:
- add a transient deferred_parent_update field to act_obj_t
- capture the target parent edge before unlinking a deleted or replaced symlink
- do that for all teardown paths, including inode and inode-generation changes
- serve that parent rescan from the pending_destroy queue, where recursion can
no longer invalidate the detect_updates() iterator
- remove the recursive symlink-specific graph walk from act_obj_destroy()
- guard parent/root dereferences when looking up or creating the helper watch

This keeps the safety goal of deferred destruction while restoring the symlink
cleanup semantics that existed before commit
262b22d82a40811ee14ed2cc3ff930d8eb45c9d4.

Closes https://github.com/rsyslog/rsyslog/issues/6576

With the help of AI-Agents: Codex

(cherry picked from commit 5c8e040b9a676bb53af373d03e45bb00f6df01fc)		 Rainer Gerhards <rgerhards@adiscon.com> no 2026-03-16

All known versions for source package 'rsyslog'

Links