Backup fails after duplicity updated to 2.0.0
jeremitu opened this issue · comments
duplicity collection-status: error: argument --gpg-options: expected one argument
Something is wrong with the backup:
gpg-options' argument must be single, quoted
It seems to be duplicity 2.0.0 problem, and there are more ahead. Solved by installing duplicity 1.2.3 to /usr/local.
# duplicity collection-status --gpg-options "cipher-algo=AES256" --log-fd 1
CommandLineError: Source should be url, not directory. Got '1' instead.
When installing duplicity==1.2.3, it was necessary to install librsync-dev
I did:
git clone --depth 1 --branch rel.1.2.3 https://gitlab.com/duplicity/duplicity.git
sudo apt install librsync-dev
cd duplicity
python3 setup.py build
sudo python3 setup.py install --prefix=/usr/local
which duplicity #should be local
Rather than reverting, one could try to adapt the commands in management/backup.py to the new duplicity syntax. For the first one, to get the collection status, the following argument order seems to work:
/usr/bin/duplicity --log-fd 1 collection-status --archive-dir /home/user-data/backup/cache --gpg-options "cipher-algo=AES256" file:///home/user-data/backup/encrypted
Tried that and ran from one problem into another. We need to wait until duplicity 2.x becomes stable and standard, and break compatibility with duplicity 1,x. See also #2295
Ah, yes, I see https://gitlab.com/duplicity/duplicity/-/issues/732 that duplicity 2.0 is buggy specifically in the --gpg-options option.