sbackup 0.11.3

I'm proud to announce the third bugfix release 0.11.3 of the 0.11 series of
the Simple Backup suite.

Thanks to all who contributed to this release with coding, sending
patches, testing, reporting bugs and translating!

Series 0.11.x finally replaces the old-fashioned Simple Backup 0.10.5
with code that was developed in (Not So) Simple Backup in the meantime.
It adds some very interesting features and is ready for daily
use. Most notable enhancements are:

* fixes many, partly long standing, bugs

* implementation of a status application which presents information of
  running backups such as backup size, progress and estimated remaining time

* implementation of a GIO/GVFS backend for access of remote targets (currently
  supported is FTP, SFTP, SSH, NFS). The backend to use can be controlled
  by a GConf setting (see https://answers.launchpad.net/nssbackup/+faq/1256)

* notification window in case of not found backup destination: you can
  directly retry to use the specified destination, after mounting an
  external disk (good for creation of backups stored on external disks
  that might not be plugged in)

This release in particular fixes:

  * [Fix] LP: #645543 "Cannot concatenate str and error object" error prevents
                      incremental backups
  * [Fix] LP: #648754 Can't mount ftp location: don't fail when gvfs-fuse is
                      not available; use it only if really required
  * [Fix] LP: #653577 Error 'iter should be a GtkTreeIter' when clicking on
                      Restore with no file selected
  * refer to dependend package 'gvfs-fuse' in install and readme file
  * translations updated
  * translations added: da,el,fa,is,ja,kk,ko,kw,ro,sr,sw

See the changelog on the download page for more information.

Known issues - There are a few known issues in SBackup 0.11.x:

* when upgrading snapshots in old Simple Backup format (1.4 and older) it is
  not recommended to use these as base for successive snapshots. Make a full
  snapshot instead.
* specified log directories are not modified when using former nssbackup
  configurations. This might lead to directories named `.../nssbackup`.
* in order to use secure remote targets (SFTP, SSH via GIO) you'll have to
  add the remote machine to your trusted machines first
  (see https://answers.launchpad.net/nssbackup/+faq/1255)
* due to default security settings it is not possible to create backups at
  remote destinations which are split into several chunks when running as
  superuser (root) using the GIO backend
* No Help available on Ubuntu 8.04 Hardy (due to use of Mallard)
* if you want to install nssbackup from source code after you've had
  already installed it from PPA, you need to *Purge* the package (i.e.
  remove package and configuration files, not only remove) to avoid
  confusion of your packaging software about configuration files in
  system directories (namely /etc/dbus-1/system.d)