[arch-general] Recent logwatch update may need a news item?

[Eli Schwartz]

On 9/19/19 8:29 PM, Amish via arch-general wrote:
> Thanks but why would one parse logs to log it back to logs?

I'm not sure what this statement means, but there is no "parsing", and
the only "logs" are the systemd ones. Just emailing the logs doesn't
constitute re-logging it to a new log.

> The default behaviour of earlier version of logwatch was to send email
> to root. (via cron)

The default behavior of earlier versions of the logwatch archlinux
package, yes. What about the default behavior of logwatch itself?

Also, like, the vast majority of system logs aren't automatically
emailed to root by the software itself. I guess the vast majority of
logs in a systemd-based distro aren't emailed at all (because unlike
cron, systemd does not do this by default).

> So I guess if the timer was meant to be drop in replacement for cron
> then it should e-mail too.

Who said it was supposed to be a drop-in replacement for cron? The
impression I got from looking at https://bugs.archlinux.org/task/56357
is that the timer was supposed to be a "migration from cron installs to
the upstream systemd service".

I really don't see why you think archlinux should be opinionated and
modify upstream service files. I hear your argument that the package
should have a post_upgrade message.

-- 
Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1601 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20190920/a3c6aa2b/attachment.sig>