Description of problem: The logwatch script in bacula 2.0 only allows for a Range setting of "yesterday", "today", and "all". The main logwatch program in EL5 allows for any string that Date::Manip can parse. Version-Release number of selected component (if applicable): logwatch-7.3-8.el5 bacula-director-common-2.0.3-10.el5 Steps to Reproduce: 1. Install bacula and logwatch 2. Set a range in /etc/logwatch/conf/logwatch.conf that is not "yesterday", "today", or "all". 3. run logwatch Actual results: The logwatch email will contain errors in the Bacula section, like "Use of uninitialized value in string eq at /etc/logwatch/scripts/services/bacula line 74, <STDIN> line 433." Expected results: Proper logwatch output for bacula Additional info: This was discussed in http://bugs.bacula.org/view.php?id=1315 and fixed in upstream's git 9321c4aea3020df015addaa899cb972796592222. If the EPEL5 maintainers want to stay on 2.0, I think this would be appropriate to backport.
bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5
Package bacula-2.4.4-5.el5, bacula-docs-2.4.4-4.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing bacula-2.4.4-5.el5 bacula-docs-2.4.4-4.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6421/bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5 then log in and leave karma (feedback).
bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5
bacula-2.4.4-7.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bacula-2.4.4-7.el5
bacula-2.4.4-7.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.