Public bug reported:

>From Debian bug #629931:

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.

** Affects: backintime
     Importance: Undecided
         Status: New

** Affects: backintime (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: backintime (Debian)
     Importance: Unknown
         Status: Unknown

** Bug watch added: Debian Bug tracker #629931
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629931

** Also affects: backintime (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629931
   Importance: Unknown
       Status: Unknown

** Also affects: backintime (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806143

Title:
  warning about config update is not written to stderr

To manage notifications about this bug go to:
https://bugs.launchpad.net/backintime/+bug/806143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to