Package: backupninja Version: 0.9.4-4 Severity: critical Justification: causes serious data loss
The mysql backup handler happily overwrites your existing sql.gz files with empty tarballs even in situations such as: 1) mysqldump does not exist 2) mysql is not running ...etc. This just bit me when #2 happened due to a crash in mysql which involved corrupted data. Fortunately I have multiple snapshots of the sql.gz files... It looks like this might only happen when you specify the names of the databases you wish to back up. Also, I have only tested this using the "mysqldump" method. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5.jjf1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages backupninja depends on: ii bash 3.1-5 The GNU Bourne Again SHell ii dialog 1.0-20060221-1 Displays user-friendly dialog boxe ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii mawk 1.3.3-11 a pattern scanning and text proces backupninja recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
