tags 381820 + moreinfo
severity 381820 normal
thanks
[ I reduce the severity to normal as I think most of the issues reported
there come from a misunderstanding of the postinst phase ]
* Cameron Horsburgh ([EMAIL PROTECTED]) disait :
> First, the configuration routine finishes half way through on
> re-installation. It asks me a few questions, but finishes after asking
> me what directories I want backed up. It didn't give me a chance to
> tell it what I didn't want backed up, or any other options after that.
That's pretty strange, I cannot reproduce that behaviour...
> I used dpkg-reconfigure to complete the configuration. That went okay
> (although I can't see an option to select the newish tar-incremental
> option which I'd like to use). However, once I finished I get the note
> asking me if I want to install the package maintainer's config or my
> own. I presume this is because the config didn't finish during
> installation.
No, that's because the post-installation phase built a new configuration
file with all the answers you gave to the debconf prompts. It wanted to
overwrite your `/etc/backup-manager.conf' file and then prompted you for
confirmation.
As you denied the replacement, the post-installation script left your
system with the _old_ conffile, and then without your new answers.
> I elected to install my own config. However, that still doesn't
> help--when I run backup-manager from the CLI it only backs up /etc and
> /boot. I did ask for /etc but not /boot, as you can see above. I do
> notice in /etc/backup-manager that these are fallback defaults if I
> choose to backup filenames with spaces, which I don't believe I've
> done.
That's because ou denied to replace your conffile. Here is what I
suggest for upgrading a backup-manager conffile : copy
/etc/backup-manager.conf to /tmp, then install the new package and
answer yes when it prompts for conffile replacement.
Then, edit both /etc/backup-manager.conf and /tmp/backup-manager.conf
and make sure everything in /etc/backup-manager.conf is ok.
For the backup targets issue, take a look at the user-guide:
2.2.1.7 BM_TARBALL_DIRECTORIES
[...]
Since version 0.7.3, this variable is replaced by the array
BM_TARBALL_TARGETS[], it's still supported for backward compatibility
though.
You can use this variable for defining the locations to backup, but you
must
not use this variable if one or more of the paths you want to archive
contain a
space.
2.2.1.8 BM_TARBALL_TARGETS
[...]
This variable holds every place you want to backup. This is the
recommanded
variable to use for defining your backup targets
(BM_TARBALL_DIRECTORIES is
deprecated since version 0.7.3).
You can safely put items that contain spaces (eg: "Program Files")
whereas you
can't with BM_TARBALL_DIRECTORIES.
You can also put Bash patterns in BM_TARBALL_TARGETS[], it will be
expanded at
runtime to find the resulting targets. For instance :
BM_TARBALL_TARGETS[0]="/home/*" will lead to backup every home's
sub-directory.
The postinst phase will only handle BM_TARBALL_TARGETS, so edit your
conffile after the installation to make sure this variable is enabled
and not BM_TARBALL_DIRECTORIES[].
Regards,
--
Alexis Sukrieh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
