giseldo/neodataset huggingface dataset:
Error when parsing exclude filelist (lp:#1409908)

[Original report](https://bugs.launchpad.net/bugs/1409908) created by **Mikhalych (zhupikov)**
```
Duplicity version 0.7.0
OS Ubuntu 14.04.1
Target: ftp (Linux)

Hello!
If i create full backup with option --exclude-filelist (filelist in attach)
duplicity geneate error:
WARNING 1
. Import of duplicity.backends.dpbxbackend Failed: No module named dropbox

NOTICE 1
. LFTP version is 4.4.13

NOTICE 1
. Чтение списка файлов exclude.txt

NOTICE 1
. Сортировка списка файлов exclude.txt

NOTICE 1
. Локальные и удалённые метаданные синхронизированы, синхронизация не
требуется.

NOTICE 1
. Время последней полной резервной копии: нету

NOTICE 1
. Чтение списка файлов exclude.txt

ERROR 30 ValueError
. Traceback (most recent call last):
.   File "/usr/bin/duplicity", line 1500, in <module>
.     with_tempdir(main)
.   File "/usr/bin/duplicity", line 1494, in with_tempdir
.     fn()
.   File "/usr/bin/duplicity", line 1343, in main
.     do_backup(action)
.   File "/usr/bin/duplicity", line 1464, in do_backup
.     full_backup(col_stats)
.   File "/usr/bin/duplicity", line 522, in full_backup
.     commandline.set_selection()
.   File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line
914, in set_selection
.     sel.ParseArgs(select_opts, select_files)
.   File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line
237, in ParseArgs
.     filelists[filelists_index], 0, arg))
.   File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line
315, in filelist_get_sf
.     self.filelist_read(filelist_fp, inc_default, filelist_name)
.   File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line
351, in filelist_read
.     for line in filelist_fp.read().split(separator):
. ValueError: I/O operation on closed file
.
If i write all of this exclude folders in command line wiyh option
--exclude duplicity work fine.

Sample Commands:
Error: duplicity full --no-encryption --exclude-filelist exclude.txt --ftp-
regular --log-file family_backup.log --progress --progress-rate 10
--volsize 700 /home/family/
lftp+ftp://useruser:q1234567@192.168.0.10/sda1/Backup/Family

Fine: duplicity full --no-encryption --exclude /home/family/Аудиокниги
--exclude /home/family/Музыка --exclude /home/family/Видео --exclude
/home/family/Семейный\ архив --ftp-regular --log-file family_backup.log
--progress --progress-rate 10 --volsize 700 /home/family/
ftp://useruser:q1234567@192.168.0.10/sda1/Backup/Family
```

Story points: 16.0
Cannot restore backup (lp:#1403375)

[Original report](https://bugs.launchpad.net/bugs/1403375) created by **Max (khaberev)**
```
Trying to restore backup from external hdd drive. Got the following error:

Traceback (most recent call last):
  File "/usr/sbin/duplicity", line 1500, in <module>
    with_tempdir(main)
  File "/usr/sbin/duplicity", line 1494, in with_tempdir
    fn()
  File "/usr/sbin/duplicity", line 1343, in main
    do_backup(action)
  File "/usr/sbin/duplicity", line 1428, in do_backup
    restore(col_stats)
  File "/usr/sbin/duplicity", line 691, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 538,
in Write_ROPaths
    ITR( ropath.index, ropath )
  File "/usr/lib/python2.7/site-packages/duplicity/lazy.py", line 344, in
__call__
    last_branch.fast_process, args)
  File "/usr/lib/python2.7/site-packages/duplicity/robust.py", line 37, in
check_common_error
    return function(*args)
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 591,
in fast_process
    ropath.copy( self.base_path.new_index( index ) )
  File "/usr/lib/python2.7/site-packages/duplicity/path.py", line 433, in
copy
    other.writefileobj(self.open("rb"))
  File "/usr/lib/python2.7/site-packages/duplicity/path.py", line 609, in
writefileobj
    buf = fin.read(_copy_blocksize)
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 204,
in read
    if not self.addtobuffer():
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 229,
in addtobuffer
    self.tarinfo_list[0] = self.tar_iter.next()
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 336,
in next
    self.set_tarfile()
  File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 325,
in set_tarfile
    self.current_fp = self.fileobj_iter.next()
  File "/usr/sbin/duplicity", line 727, in get_fileobj_iter
    backup_set.volume_name_dict[vol_num],
KeyError: 144


duplicity 0.7.0
Python 2.7.9
Archlinux x64 up-to-date
ntfs -> ext4

Full restore log from:
script -c "duplicity -v9 file:///run/media/khaberev/Elements/arch/myfiles
/myfiles/1" /myfiles/restore.log
is attached
```

Story points: 6.0
duplicity does NOT close properly (lp:#1980908)

[Original report](https://bugs.launchpad.net/bugs/1980908) created by **Kenneth Loafman (kenneth-loafman)**
```
Duplicity process stays running after closing deja-dup backups app from
Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error
message shows "Another duplicity instance is already running with this
archive directory". `ps -ef | grep duplicity` shows the process still
running.
```

Story points: 6.0
snap contains python 3.8 and 3.9 libs (lp:#1965814)

[Original report](https://bugs.launchpad.net/bugs/1965814) created by **Kenneth Loafman (kenneth-loafman)**
```
Using the attached snapcraft.yaml, snap builds with conflicting libs:

$ find /snap/duplicity/current/ -type d -name 'python3*'
<snip>
/snap/duplicity/current/usr/lib/python3
/snap/duplicity/current/usr/lib/python3.8     <-- this should be here ****
/snap/duplicity/current/usr/lib/python3.9     <-- this one causes confusion
****
<snip>

Since duplicity uses _librsync*.so and that's only installed in python3.8,
it fails when python 3.9 is used, as is done on Debian 10.  It's only one
executable and should only have one version of python supplied in the snap.
```

Story points: 6.0
SMB Mount to backup directory prevents mounting parent directories of share (lp:#1962593)

[Original report](https://bugs.launchpad.net/bugs/1962593) created by **Dan Sorak (dsorak)**
```
May also apply to the "duplicity" package and is related to network
"mount"s:

To reproduce:
* Set up a writeable SMB share: smb://1.2.3.4/backup
* Create a subdir: smb://1.2.3.4/backup/UbuntuBackup
* Using "deja-dup" -> "Storage location" set:
    Storage location: Network Server
    Network Location: smb://1.2.3.4/backup/UbuntuBackup
    Folder: MyMachineBackup
* REBOOT THE MACHINE (or clear any cached mounts to "smb://1.2.3.4/backup")
* Select "deja-dup" -> "Overview" -> "Back Up Now..."
* Allow the backup to start, but not finish
* Go to Nautilus (file browser) -> "+ Other Locations"
  - At the bottom set "Connect to server" to: smb://1.2.3.4/backup

Result:
* The parent SMB directory "smb://1.2.3.4/backup" is inaccessible because
the "UbuntuBackup" subdir is currently mounted
* Can happen at semi-random times if the backup is on a schedule
* This is especially a problem when backing up remotely over a VPN which
can take a long time
* Prevents access to all parent folders of the backup folder
* Nautilus will hang, unable to mount the "backup" parent directory
* Also a problem if the "smb://1.2.3.4/backup" folder is bookmarked in
nautilus
* This problem is persistent throughout backup process and for a period of
time afterwards until the mount to "UbuntuBackup" times out or the backup
process exits

Possible solutions:
* Add a configuration option to deja-dup/duplicity to specify the "Share
root" and mount that first before accessing the configured "Network
Location"
* Have deja-dup or duplicity attempt to mount the parent
directory/directories first by starting at the root of the SMB share and
walking down the directory tree until a successful mount is made. In the
above example, start by attempting to mount "smb://1.2.3.4/backup" first
and then "smb://1.2.3.4/backup/UbuntuBackup" (in the case of deeper folder
structures, try each one successively)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deja-dup 40.7-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  1 08:51:47 2022
ExecutablePath: /usr/bin/deja-dup
InstallationDate: Installed on 2021-09-13 (168 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64
(20210819)
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)
```
Original tags: amd64 apport-bug backup focal network smb

Story points: 6.0
Deja-dup has stopped working since upgrade to Ubuntu-21.04 (lp:#1946528)

[Original report](https://bugs.launchpad.net/bugs/1946528) created by **sTiVo (stevecoh1)**
```
 I upgraded to Ubuntu-21.04 (from 20.04->20.10->21.04) and now I find that
my deja-dup backup is failing with the following obscure error message:

Failed to read /tmp/duplicity-6k2ojcdb-tempdir/mktemp-s39ei7up-2: (<class
'EOFError'>, EOFError('Compressed file ended before the end-of-stream
marker was reached'), <traceback object at 0x7f80484aaa00>)

A search on this error message produced a similar issue:
https://answers.launchpad.net/duplic...uestion/693039 from 2020 which died
for a lack of response.

Can someone provide me some help on how to proceed here to get my backups
working again? Thanks.

OS: Ubuntu 21.04
```

Story points: 8.0
duplicity falsely reports B2 python SDK not installed, fails backup to B2 (lp:#1933540)

[Original report](https://bugs.launchpad.net/bugs/1933540) created by **Kenneth Loafman (kenneth-loafman)**
```
Description:    Ubuntu 21.04
Release:        21.04

duplicity:
  Installed: 0.8.17-1build1
  Candidate: 0.8.17-1build1
  Version table:
 *** 0.8.17-1build1 500
        500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
        100 /var/lib/dpkg/status

What I expected to happen: duplicity successfully backs up to B2 when I run
`duplicity ~ b2://<redacted>@<redacted>`

What happened instead: duplicity immediately fails with the error
"BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)".


duplicity was working fine for me backing up my local machine to BackBlaze
B2, when I was running 20.10. After upgrading to 21.04, now I get this
problem.

Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I
do use pyenv to manage different Python versions but pyenv global is set to
system when I use pip to try to troubleshoot this, so this should not be
interfering

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: duplicity 0.8.17-1build1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Regolith:GNOME-Flashback:GNOME
Date: Thu Jun 24 12:28:50 2021
InstallationDate: Installed on 2020-11-20 (215 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=alacritty
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: duplicity
UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago)
```
Original tags: amd64 apport-bug hirsute

Story points: 6.0
too many files open (lp:#1933261)

[Original report](https://bugs.launchpad.net/bugs/1933261) created by **Heiner Kuhlmann (heiner-k)**
```
System: openSUSE Leep 15.2 / duplicity 0.8.11

To prevent useless hints, I am aware that my problem with the mounted
dav directory can easily be solved by

duplicity / webdavs://....

But webdav is not the problem, it is a shortcoming in duplicity.

This problem occurs only in special cases:

  duplicity / file:///Save/DAV_mount

/Save/DAV_mount is mounted via davf2.

The system log reports the error

  open files exceed max cache size by ...

In the directory /var/cache/davfs2/webdav.magentacloud.de+Save-Cloud+root/
there are many files like
duplicity-inc.20210622T104338Z.to.20210622T142854Z.vol17.difftar.gpg-kIVuGX
...
duplicity-
inc.20210622T104338Z.to.20210622T142854Z.vol140.difftar.gpg-2FrxIW

Almost all of the files have already been transferred to the webdav
directory and could be deleted in the dav cache. dav cannot delete because
these files are still open.

The cause is probably that duplicity keeps a lot of files open even though
they have already been completed.

Presumably, duplicity does not close files immediately after they have been
completely written.

In the spirit of good programming practice, every resource - including open
files - should be released as soon as possible.
```

Story points: 6.0
Certain files aren't restored, despite being in the repository (lp:#1919054)

[Original report](https://bugs.launchpad.net/bugs/1919054) created by **Xenon Fiber System (xenonfiber)**
```
I'm running a restore operation on a local repository, and I'm able to get
the vast majority of the files extracted, but there are a couple that have
a fatal error.

python2: ERROR: (rs_file_copy_cb) unexpected eof on fd494
python2: ERROR: (rs_job_complete) patch job failed: unexpected end of input
Error 'librsync error 103 while in patch cycle' patching [FILE]

In case it's relevant, all the successfully extracted files still throw
another error, but from what I've read, it's just due to the ownership
permissions not being successfully restored, but otherwise extracting just
fine:

Error '[Errno 1] Operation not permitted: '/[FILE]'' processing [FILE]


Duplicity 0.7.17
Python 2.7.17
Linux Mint 19.3
ext4 Filesystem
```

Story points: 6.0
Very bad performance when deleting files from mediafire backend (lp:#1919020)

[Original report](https://bugs.launchpad.net/bugs/1919020) created by **Jose Riha (jose1711)**
```
Under certain conditions the performance of removing old backups from
mediafire backend can be extremely bad - it can take hours to process such
request.

The main contributor to this slowdown is a combination of
 - using mediafire in multibackend and the fact that file lists are not
cached per store
   +
 - multiple calls to list mediafire folder contents
   (e. g. in multibackend.py's _delete function or mediafire backend's
delete_file function which is still using API 1.3 for deletion. Unlike the
latest version version 1.3 does not allow to delete the file by specifying
full path and for each request the whole folder contents must be retrieved)
   +
 - large amount of files (e. g. 4 000+) in MF directory

duplicity 0.8.18
python 3.9.2
Arch Linux, x86_64
```

Story points: 6.0
Duplicity fails backups with message "SHA1 hash mismatch for file..." every single time (lp:#1894073)

[Original report](https://bugs.launchpad.net/bugs/1894073) created by **Santiago Gala (sgala)**
```
Backup has been going on ok since some days ago. Then the backups started
failing with message:

Invalid data - SHA1 hash mismatch for file:
 duplicity-inc.20200828T014540Z.to.20200829T012824Z.vol1.difftar.gz
 Calculated hash: 06f2c3af5c64b989db2507d842a64e19d1cb7206
 Manifest hash: 77788b1c0808968b82904e3b0f688143fbebe1d0

Without any way offered to take an action to proceed.
```

Story points: 6.0
override_dh_auto_install fails when building in a virtualenv (lp:#1879720)

[Original report](https://bugs.launchpad.net/bugs/1879720) created by **Mischa ter Smitten (mischa-ter-smitten)**
```
I'm trying to build duplicity (version 0.7.19) in a virtualenv. I'm using
the following steps:

sudo apt install build-essential debhelper devscripts equivs dh-virtualenv;

mkvirtualenv -ppython2 ANSPB-453;
pip install --upgrade pip;
pip install make-deb;
pip install -r requirements.txt;

sudo apt-get install librsync-dev par2 rdiff;
# dpkg-buildpackage -us -uc;
dpkg-buildpackage -us -uc -f;

The last command fails on:

rm -r debian/duplicity/usr/share/doc/duplicity-*

when building in a virtualenv this directory does not exist.

debian/duplicity/home/mtersmitten/.virtualenvs/ANSPB-453/share/doc/duplicity-0.7.19

however does.

changing the rm command to:

find debian/duplicity -path "*share/doc/*" -name "duplicity-*" -print0 |
xargs --no-run-if-empty -0 rm -r

fixes the issue.
```

Story points: 6.0
Duplicity fails backups at the end every time (lp:#1871757)

[Original report](https://bugs.launchpad.net/bugs/1871757) created by **Kenneth Loafman (kenneth-loafman)**
```
Backup seems to progress well (it takes a long time) and ends up with this
error:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1393, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1472, in do_backup
    restore(col_stats)
  File "/usr/bin/duplicity", line 728, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558,
in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521,
in integrate_patch_iters
    for patch_seq in collated:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389,
in yield_tuples
    setrorps(overflow, elems)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378,
in setrorps
    elems[i] = iter_list[i].next()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107,
in filter_path_iter
    for path in path_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121,
in difftar2path_iter
    tarinfo_list = [tar_iter.next()]
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339,
in next
    self.set_tarfile()
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333,
in set_tarfile
    self.current_fp = self.fileobj_iter.next()
  File "/usr/bin/duplicity", line 764, in get_fileobj_iter
    backup_set.volume_name_dict[vol_num],
 KeyError: 8
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-12-11 (849 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
(20171018)
Package: duplicity 0.7.17-0ubuntu1.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18
Tags:  bionic
Uname: Linux 5.3.0-42-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-06-05 (673 days ago)
UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
wireshark
_MarkForUpload: True
```
Original tags: apport-collected bionic

Story points: 6.0
Add multi core support for compression (lp:#1860200)

[Original report](https://bugs.launchpad.net/bugs/1860200) created by **Byron (byronester)**
```
Duplicity compresses and decompresses with a single process atm.
Performance can be increased by parallelizing this process. This in turn
could be done using something like mgzip.

https://code.launchpad.net/~byronester/duplicity/duplicity
```

Story points: 16.0
Duplicity 0.8.09 seems not work with S3 + https proxy (python 3 / boto bug ?) (lp:#1859200)

[Original report](https://bugs.launchpad.net/bugs/1859200) created by **Gaël Bréard (gbrd)**
```
Duplicity 0.8.09 (snap release 48) seems not work with S3 + https proxy
(python 3 / boto bug ?)

It may be related to a known bug on boto / python3 ?
https://github.com/boto/boto/issues/3561



sock.sendall("CONNECT %s HTTP/1.0\r\n" % host)  TypeError: a bytes-like
object is required, not 'str'

It work with version 0.8.08 / snap release 33
```

Story points: 6.0
Large data is failed to take backup with duplicty (lp:#1854351)

[Original report](https://bugs.launchpad.net/bugs/1854351) created by **Gangadhar (gangadhar24)**
```
We have the 103 GB data in volume and trying to take the backup, but it is
taking too much time and failed to take the backup of entire data.

duplicity 0.8.03
Data size 103 GB
endpoint is s3.us-south.objectstorage.softlayer.net
python version 3.7.3

cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.10.1


Note : one of our customer failed to take the backup of 130GB size.
```

Story points: 6.0
Duplicity doesn't install all dependancies (lp:#1853650)

[Original report](https://bugs.launchpad.net/bugs/1853650) created by **Magnus (mxvalle)**
```
Installing the duplicity package does not include all it's dependencies,
specifically the B2 backend.

When running a command like this with a freshly installed duplicity on a
freshly installed Ubuntu 19.10

`$ duplicity Photos/ b2://123:567@photos`

it returns the following error

`BackendException: B2 backend requires B2 Python APIs (pip install b2)`
```
Original tags: packaging

Story points: 12.0
PCA and Swift backends don't make use of etag (md5) (lp:#1852597)

[Original report](https://bugs.launchpad.net/bugs/1852597) created by **Kenneth Loafman (kenneth-loafman)**
```
Do PCA and Swift backends make use of etag (md5 checksum) on upload? (I
think they don't)

If not, wouldn't that be beneficial?

From OVH Public Cloud Archive reference for developers (
https://docs.ovh.com/gb/en/storage/pca/dev/#uploading-an-archive ):
"When uploading an archive to OVH Public Cloud Archive, it is very
important to verify that both the local and remote copy of the data are
indentical. This is a guarantee data received remotely is correct and that
nobody has been able to alter its content."
```

Story points: 8.0
FilePrefixError on all --exclude (lp:#1849335)

[Original report](https://bugs.launchpad.net/bugs/1849335) created by **Jay Bienvenu (jbnv)**
```
I'm getting this error for the --exclude option, no matter what I specify
to exclude and even if I --exclude-filelist. Here's an example of my trace.
I'm using duplicity 0.7.17, Ubuntu 18.04.3 LTS, Python 2.7.15+.

> duplicity --exclude .git ~/source_folder file:///target
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1380, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line
1149, in ProcessCommandLine
    set_selection()
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line
973, in set_selection
    sel.ParseArgs(select_opts, select_files)
  File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line 250,
in ParseArgs
    self.add_selection_func(self.glob_get_sf(arg, 0))
  File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line 434,
in glob_get_sf
    sel_func = self.glob_get_filename_sf(glob_str, include)
  File "/usr/lib/python2.7/dist-packages/duplicity/selection.py", line 502,
in glob_get_filename_sf
    raise FilePrefixError(filename)
 FilePrefixError: .git

> duplicity -v9
Command line error: Expected 2 args, got 0
Enter 'duplicity --help' for help screen.
Using temporary directory /tmp/duplicity-oupQbS-tempdir
```

Story points: 6.0
Fresh ubuntu 19.10 install PyDrive error (lp:#1848669)

[Original report](https://bugs.launchpad.net/bugs/1848669) created by **Ioan Cristea (krioft)**
```
The error is:
BackendException: PyDrive backend requires PyDrive installation.  Please
read the manpage for setup details.
Exception: No module named 'apiclient'

DV: 40.1-1ubuntu2
Ubuntu 19.10
Linux

python -V
Python 2.7.17rc1
```

Story points: 10.0