From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] sysklogd: upgrade 2.7.2 -> 2.8.0
Date: Fri, 16 Oct 2026 11:20:25 +0200 [thread overview]
Message-ID: <20261016092025.19560-2-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20261016092025.19560-1-jaipaul.cheernam@est.tech>
[v2.8.0][] - 2026-10-15
-----------------------
### Changes
- Add `pri` action option, e.g. `*.* /var/log/messages ;pri`, to always print
the message priority in the header, in the format in use (RFC3164 or
RFC5424). By Gavin D. Howard. The NetBSD-style `+` destination prefix is
an equivalent alternative, e.g. `*.* +/var/log/messages`, and combines with
the `-` no-sync prefix as `+-`
- Add `hostname=NAME` action option to replace the hostname in messages
logged by that action, e.g. to forward under a fixed name from a system
whose hostname changes
- Add `sd=[SD-ELEMENT]` action option to append a structured data element
to every message logged by that action. RFC5424 format only
- `logger` now parses a leading `<LEVEL>` (PRI) in input messages, e.g. for
systemd-style `daemon --foreground 2>&1 | logger` redirection
- Add security policy for reporting vulnerabilities
### Fixes
- Fix #105: UTF-8 handling with the `-8` flag. Multi-byte sequences, e.g.,
em-dash, were corrupted by byte-by-byte sanitization; complete valid UTF-8
sequences are now preserved, including the RFC 5424 BOM
- Unescape Linux `/dev/kmsg` C-style `\xHH` encoding before sanitization, so
UTF-8 in kernel messages is preserved with the `-8` flag
- Fix #104: RFC 3164 tag parsing of parenthesized tags. Surrounding parens are
stripped from complete tags, `(polkit-agent):` becomes `polkit-agent`, while
partial tags like `app(version):` are preserved
- `logger`: fix evaluation order violation, found by Coverity Scan
[UNRELEASED]: https://github.com/troglobit/sysklogd/compare/v2.8.0...HEAD
[v2.8.0]: https://github.com/troglobit/sysklogd/compare/v2.7.2...v2.8.0
Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
---
.../sysklogd/{sysklogd_2.7.2.bb => sysklogd_2.8.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/sysklogd/{sysklogd_2.7.2.bb => sysklogd_2.8.0.bb} (91%)
diff --git a/meta/recipes-extended/sysklogd/sysklogd_2.7.2.bb b/meta/recipes-extended/sysklogd/sysklogd_2.8.0.bb
similarity index 91%
rename from meta/recipes-extended/sysklogd/sysklogd_2.7.2.bb
rename to meta/recipes-extended/sysklogd/sysklogd_2.8.0.bb
index c436153d1bf..79e26126533 100644
--- a/meta/recipes-extended/sysklogd/sysklogd_2.7.2.bb
+++ b/meta/recipes-extended/sysklogd/sysklogd_2.8.0.bb
@@ -10,11 +10,11 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=5b4be4b2549338526758ef479c040943 \
inherit update-rc.d update-alternatives systemd autotools
-SRC_URI = "git://github.com/troglobit/sysklogd.git;branch=master;protocol=https;tag=v${PV} \
+SRC_URI = "git://github.com/troglobit/sysklogd.git;branch=v2.x;protocol=https;tag=v${PV} \
file://sysklogd \
"
-SRCREV = "5fb314cb9060afa3bd4eed2f0be3200f02f729e9"
+SRCREV = "e2c0c1d9585e88b1a85e3634c4dc230517f68f0e"
EXTRA_OECONF = "--with-systemd=${systemd_system_unitdir} --without-logger"
next prev parent reply other threads:[~2026-10-16 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:20 [PATCH 1/2] libarchive: upgrade 3.8.9 -> 3.8.10 Jaipaul Cheernam
2026-10-16 9:20 ` Jaipaul Cheernam [this message]
2026-10-17 10:21 ` [OE-core] " Mathieu Dubois-Briand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261016092025.19560-2-jaipaul.cheernam@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox