Actually, no. The latest and best duplicity versions are in the ppa package. Ubuntu, and others, lock the version when a release is made. For example, version 0.7.19 is the current version in the ppa, but it's not in any apt repository. Instead, much earlier versions are there and do not get fixes or improvements, so I normally recommend upgrading using the duplicity ppa with apt.
As to pip, much the same goes there. There are versions on pip that far exceed what is on the distro's apt repository. Some of those are needed to keep the duplicity backends running, since the hosts may randomly change the API after successfully getting the last version working. It's not apt I don't like, it does it's job. It's the policy of locked versions that causes me a lot of grief and needless bug reports for packages that are years older than they should be. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Won't Fix Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
