Support for Python 3.13
Appears to have been addressed in edd534bcd46b7fdbc69ed6911020e7a60d7189f8
Fix tests with numpy 2.X
This appears to have been addressed differently in a222c2de5350f6382f8803c93c3c73427c22c752
Fix usage of (?:) no capture groups
So, it appers that there may have been a fix made to texlive. I'm no longer seeing this failure.
That appears to have done the trick. Thanks!
Fails to build with lua 5.5
ps_fontfile_doc.pdf fails to build with texlive 20250308
Update --archves
I needed the following in /etc/logwatch/conf/logfiles/clam-update.conf: *OnlyService = freshclam *RemoveHeaders LogFile = LogFile = syslog LogFile = syslog.0 Archive = Archive = syslog.*.gz to really get it right for Ubuntu 22.04 I think.
Not particularly. I'm just going through various bug reports on gnuplot in Fedora and came across the CVE report related to this crash.
Any ETA on a new release with this fix? Thanks.
Ah - looks like this: a5897feadc4be73b0ffd8458556c47117bd24d03 hpgl: font name parsing overruns the string by one char if no comma is present in the font name. E.g. set term pcl set title "Title" font "sans" # no comma in font name plot x Bug 2781
What commit fixed this? It seems like this was assigned CVE-2025-3359 so it would be nice to have a reference
Python modules should either be installed in SITELIB if they are arch independant, or SITEARCH if they are arch-dependant (compiled), but not a mix of the two. Attached patch fixes this.
[rsyslogd] De-duplicate lines with time calculations
Update --archves
Update documentation to reflect that --archives is the default and allow disabling with --noarchives
My apologies, I committed that script too soon. It should just be removed completely, which I have done in master.
[logstash] Remove script - needs update to Logwatph.pm
Fix out of tree parallel builds
Use grouped make target for demo to fix out of tree parallel builds
Use grouped make target for demo to file out of tree parallel builds
[rsyslogd] Ignore "GnuTLS error: Error in the push function" - paired with other errors
[omsa] Handle peak power and new Unexpected sense messages
[systemd] Add ignore_messages option to ignore messages matching a regex
[kernel] Fix EDAC regex
[rsyslogd] Ignore additional rate-limiting message paired with other messages
[rsyslogd] Ignore additional omfwd messages paired with other messages
[nut] Ignore upsnotify message about tech that we already know about
[pam_unix] Add nx to services; Allow for username in session opened by messages for cron
[pam_unix] Add kde to dektop services; Hande "User info message"
[systemd] Update for newer systemd
[logstash] Initial version
[systemd] Ignore "Unnecessary job was removed for .*" - appears informational
[systemd] Ignore State timed out messages - followed by a failed message
[named] No need for unconfineds variable, not used
[systemd] Relax LSM BPF program attached regex
[dirsrv] Relax ACL target does not exist regex; Ignore schema-compat-plugin info messages that are at ERR level
gcc 15 enforces funtion poiniter arguments
gcc 15 enforces function pointer arguments
[named] Handle "zone not loaded due to errors; Handle "journal file is out of date; removed" separately; Ignore "New key observered for zone"
[named] handle "TCP client quota reached" messages; Expand limit regex
Fix tests with numpy 2.X
Avoid conflicting with numpy.min() by explicitly importing numpy fuctions
Remove trailing whitespace
[nut] Handle battery needs to be replaced message
[nut] Update for 2.8.2
[omsa] Ignored Administrator stopped message
[omsa] Update Patrol Read regex
[sssd] Ignore "exec_child_ex command" messages
[secure] relax regex around "gkr-pam: no password is available for user"
[secure] Ignore sshd-session messages
[rsyslogd] Handle stdout/stderr sent to journal which ends up with an extra prefix
Add format utility subroutines
[pam_unix] Use FormatHashCounts
[Logwatch.pm] Add FormatHashCounts to format output hash of item counts with thresholding
[named] Add option to ignore denied zone trasfter; Move limit reporting to detail >= 1
[systemd] Handle new Watchdog and Reexecuting requested messages
Support for Python 3.13
Replace PyEval_CallObject with PyObject_CallObject deprecated in Python 3.9 and removed in Python 3.13
[systemd] Ignore Expecting, Relabeled
[omsa] Update for newer message format
[systemd] Ignore "Watchdog running with a timeout of" message
[smartd] whitespace removal
[smartd] Handle .* Failed messages (such as Read SMART Self Test Log Failed)
[smartd] Add smartd_ignore_removal option to ignore device removal and reconnect
[smartd] Add smartd_ignore_capabilities and smartd_ignore_power options
Add Qt6Widgets to PKG_CHECK_MODULES
Add Qt6Wdigets to PKG_CHECK_MODULES_NOFAIL (Fixes #2705)
In Fedora the QtWidgets package is part of the qt6-qtbase package, so it's present. The problem is that there is no -I/usr/include/qt6/QtWidgets being added to the compile flags. But it does look like adding Qt6Widgets to the PKG_CHECK_MODULES line gets that added and allows the build to succeed.
gnuplot 6.0.0 fails to build with Qt6 on Fedora
webp_figures.gnu is missing from tar ball
Distribute webp_figures.gnu
[systemd] Handle "Reloading..."
FindPythonInterp and FindPythonLibs modules are removed
[sudo] Allow ignoring commands with arguments
[evt*] More event de-duplication
Does not work if not systemd
[clam-update] Add Last_Run_Only option
Recent update to clam-update generates unwanted reports
Fixed with 1238cd71671e291bf26e01646c77038b8ef3e8b0
You are right about $ignore_outdated, that is unrelated to this issue. I'm running with Detail = 0, so that's not the issue. The output generated is the contents of the $Status variable which is printed at any detail in the presence of Errors or Warnings. But yes, what I want it to ignore any warnings related to updating the definitions if it was later successfully able to update. So perhaps an option $last_run_only to have errors and warnings only from the last run? diff --git a/scripts/services/clam-update...
Recent update to clam-update generates unwanted reports
I'm surprised that logwatch requires journalctl to run. What os and how are you installing logwatch? What error are you getting?
[named] Ignore rpz reload messages
[nut] At Detail 0, do not alert about recovered disconnects
[nut] Track battery low messages
[rsyslogd] Handle connection closed messages wiith error message
[freeradius] Handle expired certificate login failures
[freeradius] Show wrong user detail at detail 3; Move Successful logins report lower
[freeradius] Update for FreeRADIUS 3.0; Use "client" instead of "IP"
[kernel] Ignore HANDLING IBECC MEMEORY messages
Use size_t for array index
Use size_t for array index
[systemd] Ignore "Running in initrd."
[omsa] Classify more messages as errors
I guess the first question is, what do these messages mean? Do they indicate something that needs to be fixed? Or are they purely informational? Should they be brought to the admins attention in normal operation, or only with high logwatch detail?
[named] Handle policy zone changed messages