Erich Eckner

I see the discrepancy between cron and systemd timer as the source. But I think, changing the systemd timer is wrong, because: Command line options superseed config file options. Thus, the systemd timer should not give any command line options (else you must edit the systemd timer file to change logwatch's default behaviour - editing /etc/logwatch/conf/logwatch.conf will not suffice). OTOH changing the cron file to not force mail (while breaking running systems) is ok IMHO, because you can always...

I see the discrepancy between cron and systemd timer as the source. But I think, changing the systemd timer is wrong, because: Command line options superseed config file options. Thus, the systemd timer should not give any command line options (else you must edit the systemd timer file to change logwatch's default behaviour - editing /etc/logwatch/conf/logwatch.conf will not suffice). OTOH changing the cron file to not force mail (while breaking running systems) is ok IMHO, because you can always...

oh, sry, didn't know (I should have checked more thoroughly, first ...). This issue can be closed then. Thanks

systemd timer

comment issue in syntax highlighting of shell/bash

replacing the -1 by -1.01 in line 285 of svcore/base/test/TestScaleTickIntervals.h fixes the issue for me

I can confirm this issue on archlinux32.

If it helps the decision to implement this patch: I can confirm this bug and that...