[Ftplicity-general] Log messages are written to wrong output streams

[Stefan J. <ste...@we...>]

I'm using duply to back up multiple Debian Lenny servers to some ftp
servers. I'd like to run backup jobs during the night with a cronjob.
The backup job should write to a log file and if there are any errors,
it should write in a error file. To achieve this, I'm using STDERR
(error output) to STDOUT (normal output). Below you'll see my actual
cronjob.

/usr/local/bin/duply <PROFILE> backup_verify_purge --force >
/var/log/backup/backup.log 2> /var/log/backup/error.log

Now I'm confused, because the error.log is never empty. It seems that
duply is writing some messages to STDERR which in my opinion should be
written to STDOUT.

When running duply <PROFILE> backup_verify_purge --force with log
level 5 configured in /etc/duply/<PROFILE>/conf, duply writes gpg
messages, which appear while verifying backup, to STDERR instead of
STDOUT.
When running the same command with standard log level 4 and if there
are no old backup sets to purge, duply writes the message "No old
backup sets found, nothing deleted." to STDERR.

Another example: when files are changing while duply is verifying
backup, at the end of verifying, a message similar to the following is
written to standard output:

Verify complete: 93898 files compared, 18 differences found.
--- Finished state FAILED (code 1) at 15:24:04.632 - Runtime 00:11:50.866 ---

Shouldn't this message be written to error output because in fact,
verification is failed and the system administrator should be notified
about this?

Is this a bug or is there anything I can do to get duply writing to
the correct output?

Thanks for your help!

Regards, Stefan