Package: backintime-common Version: 1.0.6-1 Severity: normal Yesterday I found out that backintime did not perform backups since I upgraded to wheezy. My cron script did not send a warning so I was curious why backups silently fail.
It seems that backintime does not print warnings to stderr, so redirecting output to /dev/null also dismisses any warnings: ----- # /usr/bin/backintime -b > /dev/null # /usr/bin/backintime -b Back In Time Version: 1.0.6 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. INFO: The application needs to change the backup format. Start the GUI to proceed. (As long as you do not you will not be able to make new snapshots!) WARNING: Backup not performed ----- Please write warning messages like these to stderr so that backup errors can be detected easily. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages backintime-common depends on: ii cron 3.0pl1-116 process scheduling daemon ii python 2.6.6-14 interactive high-level object-orie ii python-support 1.0.13 automated rebuilding support for P ii rsync 3.0.8-1 fast remote file copy program (lik backintime-common recommends no packages. backintime-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
