…empty lists Previously a list accepting option that was set to an empty string would generate a list with a single empty-string vaue. This would cause confusing errors and require additional checks to work around. This patch ensures force_list will return an empty list of a value is a false value. so "option = " is equivalent to "option = ,"
When determining the filename where a backup should be stored, the xtrabackup plugin only considered values for stream of 'tar' and 'xbstream', so when using the 1.0.6 default value of stream = yes, this would generate an empty backup. This patch ensures we're always comparing the stream value through determine_stream-method() so we have a consistent view of the real backup method request, where boolean true values map to 'tar' and false values map to a non-streaming method.
Initially the xtrabackup changes in 1.0.8 only accept stream = (yes,no,tar,xbstream), but this patch ensures that we handle the various boolean options the old v1.0.6 config format allowed so backwards compatibiity is preserve across minor releases.
1.0.7 introduced a regression that did not call backupset.update_symlinks() properly when running a manually "holland purge". This did not affect the "auto-purge" that usually occurs during "holland backup". Additionally this suppresses some warnings when incorrect validation is done of the individual backup.conf files during the purge process.
This should now build cleanly across ubuntu lucid/10.04+ and on debian/squeeze+ python-support will be used on lucid, and dh_sphinxdoc is not run on distributions that have python-sphinx < 1.0.7+dfsg. On older distributions lacking dh_sphinxdoc, we manually install the documentation as needed and attempt to patch up the same files as dh_sphinxdoc
Previously this was pre/post/backup-failure. This is more consistent with the implementation in the amsterdam branch.