forwarded 567553 http://bugzilla.backup-manager.org/show_bug.cgi?id=243 thanks
Am 29.01.2010 um 19:15 schrieb Michael Below: > Package: backup-manager > Version: 0.7.9-1 > Severity: normal > > This bug report is related to #567477. In that bug report I am > quoting an error message: > > /etc/cron.daily/backup-manager: > When validating the configuration file /etc/backup-manager.conf, 1 > warnings were found. Yeah, I had actually seen that warning myself when I tested the package and reported it upstream. > In the same bug report, the configuration of backup-manager is > reported as follows: > > -- debconf information: > backup-manager/upload-key: > backup-manager/name-format: long > backup-manager/upload-hosts: > backup-manager/upload-user-ftp: > backup-manager/cron_frequency: daily > backup-manager/cron_d_remove_deprecated: false > backup-manager/blacklist: /var/archives > backup-manager/time-to-live: 5 > backup-manager/burning-maxsize: 650 > backup-manager/encryption_recipient: > backup-manager/transfert_mode: scp > backup-manager/dump_symlinks: false > backup-manager/upload-user-scp: bmngr > backup-manager/burning-device: /dev/cdrom > backup-manager/upload-dir: /var/archives/uploads > backup-manager/enable_encryption: false > * backup-manager/directories: /home/mbelow > * backup-manager/repo_group: root > backup-manager/filetype: tar.gz > * backup-manager/repo_user: root > * backup-manager/backup-repository: /var/archives > backup-manager/burning-method: CDRW > backup-manager/burning-enabled: false > backup-manager/want_to_upload: false > > 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 suspect this is rather because the debconf settings are not updated when you change /etc/backup-manager.conf by hand. The debconf handling needs a complete overhaul. :-( > I had changed the config file by hand, but AFAIK it was correct (it worked). > > The actual config file was: Thanks for including it. 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". If you copy the following lines to /etc/backup-manager.conf: --8<---------------cut here---------------start------------->8--- # Which level of messages do you want to log to syslog? # possible values are : debug,info,warning,error export BM_LOGGER_LEVEL="warning" --8<---------------cut here---------------end--------------->8--- the warning should go away. Sven -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
