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/+archive/testing Frankly, this is not recommended if you care about your backup, as it is testing code. Else wait a bit. I hope to release a band-aid 10.3 that will just always pass --allow-source- mismatch (11.0 will actually ask user). ** Changed in: deja-dup Importance: Undecided => Medium ** Changed in: deja-dup Status: New => Fix Committed ** Changed in: deja-dup Milestone: None => 11.0 ** Changed in: deja-dup Assignee: (unassigned) => Michael Terry (mterry) ** Also affects: deja-dup/10 Importance: Undecided Status: New ** Changed in: deja-dup/10 Importance: Undecided => Medium ** Changed in: deja-dup/10 Status: New => Triaged ** Changed in: deja-dup/10 Assignee: (unassigned) => Michael Terry (mterry) ** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- 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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
