Should not allow ~/.cache/deja-dup directory to be ignored

[Dave Barker]

By default deja-dup backs up the user's home directory, nearly in its entirety. I went through my files and directories manually excluding things that didn't need to be backed up. One thing I excluded was ~/.cache . This broke deja-dup, backups appeared to work fine but then an error was always shown at the end.

I believe there should be a warning when ~/.cache/deja-dup is going to be ignored, or perhaps it should be impossible. I also think that there should be some mention what the function of the directory / files within it are so that the user can understand what is going on.

(I have since reconfigured the application to only back up one "Dropbox" directory and put / linked to important files there. Therefore the problem no longer affects me, but I think it would likely affect other new users.)

1. Ubuntu 15.04
2. 34.0

[Vej (vej)]

It should be impossible to exclude ~/.cache/deja-dup from the Backup. Does anyone experience this bug with a more recent version of Déjà Dup?

If so please add the following information:

1. The distribution of Linux you're using:
    lsb_release -d

2. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

    (if on Fedora or other RPM-based systems:)
    rpm -q deja-dup duplicity

3. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details):
    gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

4. The file /tmp/deja-dup.log after running the line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):
    DEJA_DUP_DEBUG=1 deja-dup --restore | tail -n 1000 > /tmp/deja-dup.log

[Launchpad Janitor (janitor)]

[Expired for Déjà Dup because there has been no activity for 60 days.]