Thanks. The main advantage of sticking with apt is unattended-upgrades makes it easy to be sure security updates are applied automatically. I’m not familiar with a similar solution for pip, and it sounds like “upgrade everything” isn’t that straightforward (according to https://github.com/pypa/pip/issues/3819).
Any idea why the 0.7.14 release works? Was there a refactoring that extracted out the B2 code? Perhaps a warning when upgrading about any removed libraries would help future upgraders. ** Bug watch added: github.com/pypa/pip/issues #3819 https://github.com/pypa/pip/issues/3819 -- 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: In Progress Status in duplicity package in Ubuntu: New 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
