Package: backupninja Version: 0.5-2 Severity: important
When a fatal error is found (for instance, wrong permissions in /etc/backup.d), the main script just exits, which means no email is sent to report the problem. This is an important bug, since that means the user can remain unaware of a problem that prevents his backups from happening normally. This happens because the 'fatal' function does an 'exit 2' line 113 of /usr/sbin/backupninja. Since all work happens in the same process (scripts are sourced), this mean backupninja just exits in that case, preventing any further action like sending the report email. Just commenting out the exit seems to be a fine solution, at least temporarily. Probably discussion with upstream is needed to decide what is the proper behaviour in all cases. That is, is it ever important that part of the script is skipped when a fatal error is found? In any case, it should definitely not just finish the whole script. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.6-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages backupninja depends on: ii gawk 1:3.1.4-2 GNU awk, a pattern scanning and pr ii mawk 1.3.3-11 a pattern scanning and text proces -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
