FS#34156 - [duplicity] Fix dependencies

Attached to Project: Community Packages
Opened by Balló György (City-busz) - Tuesday, 05 March 2013, 08:32 GMT
Last edited by Balló György (City-busz) - Saturday, 06 April 2013, 16:52 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


I propose the following changes for dependencies:
The core dependencies are gnupg, librsync and python2.

Many backends have its own dependencies, which are currently not listed in depends or optdepends. I think these should be listed in optdepends, except the most commonly used FTP and SSH backend's dependencies (ncftp and python2-paramiko), which could stay in depends.

The python2-gnupginterface is not used by duplicity, because it uses its own patched version located in /usr/lib/python2.7/site-packages/duplicity/gpginterface.py

So my proposal:

depends=('gnupg' 'librsync' 'ncftp' 'python2-paramiko')
optdepends=('lftp: FTPS backend'
'python2-boto: Amazon S3 backend'
'python2-gobject: GIO backend'
'gvfs: GIO backend'
'python2-gdata: Google Docs backend'
'python2-httplib2: Ubuntu One backend'
'python2-oauthlib: Ubuntu One backend'
'rsync: rsync backend')


This task depends upon

Closed by  Balló György (City-busz)
Saturday, 06 April 2013, 16:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in version 0.6.21-2
Comment by Jorge Barroso (jorge_barroso) - Tuesday, 05 March 2013, 09:43 GMT
I agree with python2-gnupginterface removal, if it has duplicity. And with some optepends moving like "ubuntu" ones or amazon, the other ones... well, at consumer likes... TUs and developers will decide