[backup-manager] RFH: Please review Debconf templates
Hello, thanks to my previous mail, I have now a templates
file in a better shape.
Find it attached.
It seems to me that it's near to be DTSG compliant, could you review it
and tell me if I can go on and ask translation teams to update their po
Thanks for your time.
Please CC me as I'm not subscribed to i18n.
Alexis Sukrieh <firstname.lastname@example.org>
« Quidquid latine dictum sit, altum sonatur. »
Whatever is said in Latin sounds profound.
_Description: Archives location:
Please enter the name of the directory where backup-manager will
store the generated archives ?
The size of archives may be rather important so you should store them
on a disk with enough available space.
Choices: tar, tar.gz, tar.bz2, zip
_Description: Archives storage format:
_Description: Do you want to dereference symlinks?
The tar, tar.gz and tar.bz2 filetypes may dereference the symlinks in
generated archives. Doing so is likely to generate huge archives.
_Description: Directories to skip in archives:
Please enter a space-separated list of directories which should not be
_Choices: long, short
_Description: Archives name format:
Files generated by backup-manager may use different file naming
The long format is "host-full-path-to-directory.ext" while the short
format only uses the last directory name. For instance, /home/me
would be named me.tar.gz.
_Description: Age of kept archives (days):
Please choose the number of days backup-manager will keep the files
before purging them. Combining several directories and a large number of
days for keeping them may lead to huge archives.
Default: /etc /home
_Description: Directories to backup:
Please enter a space-separated list of all the directories you want
You should rather to enter several subdirectories instead of the
parent in order to have more pertinent files in your backup repository.
For instance, "/home/user1 /home/user2 /home/user3" is more appropriate
than "/home" alone.
_Description: Do you want to enable automatic burning?
Backup-manager can burn archives when it is launched.
Be aware that choosing this option will cause backup-manager to try
burning daily archives on the selected media, which must be present
at that time.
Choices: cdrom, dvd
_Description: Burning media:
Choosing "cdrom" will require the cdrecord program while "dvd" needs
_Description: Device to use for burning data:
_Description: Maximum size of your media (Mb):
Choices: CDRW, CDR
_Description: Burning method:
When burning data, backup-manager will try to burn the whole archives
repository. If it does not fit in the media, it will try to burn only the
daily generated archives.
The CDRW method will first blank the media and then burn the data.
The CDR method will only burn the data, assuming that the media is empty.
_Description: Do you want to enable the backup-manager's uploading system ?
If you want, you can choose a remote host where archives will be
uploaded daily (either by ftp or scp).
Choices: scp, ftp
_Description: Which transfer mode do you want to use?
You can choose the way files will be uploaded.
If you choose the ftp mode, you'll be prompted for a password, whereas scp
will use key authentification (see man ssh-keygen for details on scp
_Description: Where to upload the archives?
Enter here a list of host where backup-manager will upload daily the
Note that you can specify either FQDN or IP addresses.
_Description: Enter the scp user's login:
To enable scp transfer, you have to set up a user which exists on both
remote and local hosts. This is needed for key authentification.
Note that this user must have a ssh key on the local host and the remote
hosts must have the user's public key listed in its authorized_keys file
(see man ssh-keygen for details).
_Description: User does not exists!
You have scpecified a user that does not exist on your system. Note that
the user you choose for scp transfer has to exist on both local and
I won't ask for a user anymore, run dpkg-reconfigure backup-manager when
you have a valid user for scp transfer.
_Description: Enter the FTP user's login:
Enter the FTP user to use for uploading files to remote hosts.
_Description: Enter the private key file to use for ssh authentification:
Despite of the ftp transfer mode, ssh doesn't require a password. The
authentification is based on the ssh key.
You can specify a ssh private key to use for the scp transfer.
Don't forget to add the user's public key to the remote host's
authorized_keys file (see ssh-keygen (1) for details about ssh key
_Description: Enter the FTP user's password:
Enter the password of the FTP user to use for uploading files to remote
_Description: Enter the remote host's repository:
You can choose where files will be stored on the remote host.
__Choices: hourly, daily, weekly, monthly
_Description: Cron frequency:
Please choose the cron frequency.
You can choose wether backup-manager should be run hourly, daily,
weekly or monthly.