warning about config update is not written to stderr

[Jonathan Wiltshire]

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Germar (germar)]

This was fixed in 1.0.26