The bizarre socket.getfqdn behavior is detailed in this python bug: https://bugs.python.org/issue5004
The BorgBackup maintainer at the end of the thread ended up replacing their use of it - which seems similar to Duplicity's - with this: https://github.com/borgbackup/borg/pull/3484/commits/9b0d0f3127289fc3bbe620e8adce8038ed594e9f#diff-4b53f84e19a3bb376bf2202371ed269aR188
The bizarre socket.getfqdn behavior is detailed in this python bug: https:/ /bugs.python. org/issue5004
The BorgBackup maintainer at the end of the thread ended up replacing their use of it - which seems similar to Duplicity's - with this: https:/ /github. com/borgbackup/ borg/pull/ 3484/commits/ 9b0d0f3127289fc 3bbe620e8adce80 38ed594e9f# diff-4b53f84e19 a3bb376bf220237 1ed269aR188