I disagree this bug is a dupe of 1100092.
That one is marked as fixed in 25.5, but I just tried 25.5 and my problem isn't fixed.
deja-dup starts duplicity with the following command:
/usr/bin/python /usr/bin/duplicity list-current-files --gio sftp://user@host-ip/remote-dir --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/tmp/deja-dup-MNBIUW/deja-dup --tempdir=/home/kaie/.cache/deja-dup/tmp --log-fd=22
As you can see, deja dup 25.5 makes the decision to use directory /tmp/deja-dup-MNBIUW/deja-dup - which is the one that will get multiple gigabytes, and eventually abort with "no space left in /"
I disagree this bug is a dupe of 1100092.
That one is marked as fixed in 25.5, but I just tried 25.5 and my problem isn't fixed.
deja-dup starts duplicity with the following command:
/usr/bin/python /usr/bin/duplicity list-current-files --gio sftp:// user@host- ip/remote- dir --verbosity=9 --gpg-options= --no-use- agent --archive- dir=/tmp/ deja-dup- MNBIUW/ deja-dup --tempdir= /home/kaie/ .cache/ deja-dup/ tmp --log-fd=22
As you can see, deja dup 25.5 makes the decision to use directory /tmp/deja- dup-MNBIUW/ deja-dup - which is the one that will get multiple gigabytes, and eventually abort with "no space left in /"