Comment 34 for bug 1217959

It seems deja-dup (or duplicity) has a problem with backup folders that are either symlinks and/or bind mounts.

Please see my comment #33 above regarding my situation. Here, /home/[user] is symlinked to /mnt/data/[user] and no backup is performed - it just skips it failing with the error this issue here is about. Most other people here say, they symlinked/over-mounted ~/.cache. In their case, it backups and then fails. In my case, it fails immediately.

As a test, i added /mnt/data/[user] (the source of the bind mount; thus the same files) to the backup folders. It is now backing up.. it takes some time as it's initial.. But i bet it will also fail with the same error, as ~/.cache is still on the bind mount (as /home/dn [the bind mount target] is still in the backup set)..

I think we should rename this issue to clarify.. I suggest duplicity/deja-dup are not correctly handling symlinks and/or bind mounts. Just a guess, but would make sense.. how to be sure?