This bug was fixed in the package deja-dup - 11.1-0ubuntu1
---
deja-dup (11.1-0ubuntu1) lucid; urgency=low
* New upstream release
- Fixes some restore issues (LP: #483631 and LP: #481582)
- Can delete old backups (LP: #325005)
- Can cleanly handle changed hostnames (LP:
** Changed in: deja-dup
Status: Fix Committed => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Committed
--
Changed host name prevents backup
https://bugs.launchpad.net/bugs/454591
You received this bug notification because you are a member of Ubuntu
Bugs, which
You got the message on restore?
If you want to workaround this, either use the same hostname as before
or backup to a different directory. You should be able to restore from
the old files by pointing to the old directory again. But if you're
seeing this on restore... Might be a different issue.
Hi all, I've tried to restore my test data into a VM with karmic (part
of doing my upgrade) but I've had the same source mismatch error.
I got an error message in karmic that I should use this duplicity
option, but using a terminal I get the following:
karmi...@karmicvm:~$ deja-dup --allow-source
Good point actually. Yeah I think I will have to backup to a different
folder. It's just that a full backup obviously takes longer than an
incremental one.
On a side note, it's really nice to see how involved you are with this
project. It's really nice to see when the lead of a project gets so
inv
Actually, upon reflection, always setting --allow-source-mismatch could
be bad. A user might reasonably try to backup two computers to the same
folder. With --allow-source-mismatch, the backups would keep flopping
back and forth between a backup of one computer vs. the other. And the
11.0 soluti
I've fixed this in the hopefully-soon-to-be-released 11.0. I'll open a
task for a workaround for the 10 branch, hopefully to be finished in
time for Karmic.
In the meantime, if you want to try the new 11.0 to work around this,
you can using the testing PPA: https://launchpad.net/~deja-dup-
team/+
