Déjà Dup

  1. Bug #1641423
  2. Comment #3

Comment 3 for bug 1641423

Revision history for this message
Vej (vej) wrote : Re: Back up failed with message: Failed to execute child process "duplicity" (No such file or directory)

I could verify this on a fresh virtual machine with Ubuntu 16.04.1.

See following excerpt from apt-cache show deja-dup shows that we do not depend on duplicity
Package: deja-dup
Priority: optional
[...]
Version: 34.2-0ubuntu1
Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.4), libdbusmenu-glib4 (>= 0.4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.16.2), libnautilus-extension1a (>= 1:2.91), libnotify4 (>= 0.7.0), libpackagekit-glib2-16 (>= 0.8.10), libpango-1.0-0 (>= 1.14.0), libpeas-1.0-0 (>= 1.0.0), libsecret-1-0 (>= 0.7), libunity-control-center1 (>= 14.04.0), libunity9 (>= 3.4.6), dconf-gsettings-backend | gsettings-backend, adwaita-icon-theme
Recommends: policykit-1
Suggests: deja-dup-backend-cloudfiles, deja-dup-backend-gvfs, deja-dup-backend-s3, duplicity (>= 0.6.23)

I think duplicity should be a dependency of deja-dup, to make it very hard to install deja-dup without duplicity. I'm still wondering why and when duplicity has been excluded from my installation of 16.04.1-desktop-i386.

Will set to "Critical", because it prevents new users of 16.04 from using the software at all.