Changed host name prevents backup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Fix Released
|
Medium
|
Michael Terry | ||
10 |
Won't Fix
|
Medium
|
Unassigned | ||
deja-dup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I know that this is intended behaviour for duplicity. However, I have recently installed Karmic and in doing so I changed my host name to something more imaginative. I tend to keep the same home partition when I upgrade so all my Déjà Dup setting where kept. I thought I would be able to backup but instead I get this error about the hostname mismatch. I could probably over come this by dropping to the commandline and adding the option --allow-
The steps to reproduce are easy. Backup with one computer then try and backup to the same place with a different hostname.
Just for completeness sake:
The message:
Fatal Error: Backup source host has changed.
Current hostname: rincewind
Previous hostname: sams-desktop
Aborting because you may have accidentally tried to backup two different data sets to the same remote location, or using the same archive directory. If this is not a mistake, use the --allow-
dpkg-query -W deja-dup duplicity:
deja-dup 10.2-0ubuntu1
duplicity 0.6.05-0karmic1
lsb_release -d:
Description: Ubuntu karmic (development branch)
Related branches
Changed in deja-dup: | |
status: | Fix Committed → Fix Released |
Changed in deja-dup (Ubuntu): | |
status: | New → Fix Committed |
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).