FTR, the "Fix Released" status visible here on the Debian bug is
misleading, it was closed because change was rejected by upstream.
Also, if changing the default is undesirable, can upstream please
reinstate the knob so that those who would like to take advantage of the
full potential of their
I tend to avoid bind-mounts because they confuse disk usage calculation
programs.
What I ended up doing was use "usermod" to set the home to canonical path.
deja-dup works now, and surprisingly I haven't notice any other app break
(so far).
2018-03-04 21:18 GMT+01:00 Vej
Kirk, I think you missed my update #95, which explains the root cause.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup
I'm wondering whether something like wrapping the Path.build_filename
call located in libdeja/OperationVerify.vala:connect_to_job in a
realpath() would be enough to fix this issue.
Unfortunately I don't know vala well enough to test this idea.
--
You received this bug notification because you
vej, it affects me as well, using 34.3-1
Attaching the log.
In there one can see:
DUPLICITY: ERROR 19
DUPLICITY: . home/porridge/.cache/deja-dup/metadata not found in archive - no
files restored.
And once I think about it, it makes sense, since /home is a symlink to
/srv/home, and the
5 matches
Mail list logo
