On all target releases, I've reproduced the bug with the old logwatch version, and verified the issue is resolved with the new logwatch version.
On all target releases, I've reproduced the bug with the old logwatch version, and verified the issue is resolved with the new logwatch version.