From the OP's message:
> ...
> This is not what was set in /etc/backup-manager.conf at that time.
> For me it looks like the config file is not read, maybe because of
> the warning, and debconf uses some kind of defaults for its report.
> I had changed the config file by hand, but AFAIK it was correct ...
The config file is read. The warning is unrelated to this issue. Changes
by hand do not reflect to debconf data and this is by design: one has to
call debconf to update information and this currently is done by using:
dpkg-reconfigure <package>
So this part of the report is not a bug of backup-manager. It is a common
to all packages behaviour when a configuration file is edited by hand.
From the maintainer's message:
> ... In version 0.7.9 a new variable
> BM_LOGGER_LEVEL was introduced, and if that variable is not defined in
> backup-manager.conf you receive that incomprehensible warning. It seems
> that is because logging and warnings are disabled until the sanitizing
> script (/usr/share/backup-manager/sanitize.sh) sets BM_LOGGER_LEVEL to
> the default value of "warning".
Correct and indeed this is a bug, in the sense that all warnings/errors
should be reported from the beginning, not just the final summary message
about the total number of errors (the reporting is per-se a feature, not
a bug).
This is easily fixed by cut+paste of the BM_LOGGER block in lib/sanitize.sh
from the end where currently is to the top of the checking code. I will
prepare a patch for the next-to-be-uploaded version asap, so that we can
close this bug then.
Cheers,
George
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
