To Vej's points: > Fix the problem, that accepting the changed hostname is not persistent
It *should* already be persistent. In the sense that each time duplicity backs up, it writes the current hostname to the manifest and checks against that going forward. I think it just looks like it's not persistent because the fqdn can frequently change. > Find a solution for the problem, that the hostname from socket.getfqdn() does not always match the one from socket.gethostname() I've proposed a MR upstream to use gethostname instead of getfqdn. With this change, hopefully we don't need to do anything on our end. https://gitlab.com/duplicity/duplicity/-/merge_requests/24 I'll close this deja-dup ticket, since I think we can just let duplicity handle this. ** Changed in: deja-dup Status: Confirmed => Invalid ** Changed in: deja-dup (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268182 Title: Computer name changed To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1268182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
