Duplicity 0.7.15 and later fail if using the Backblaze B2 backend. This was tested with app-backup/duplicity-0.7.17. duplicity was called with: duplicity --encrypt-key ${SIGN_KEY} --volsize ${VOLSIZE} --max-blocksize=20480 ${sourcedir} b2://${ACCID}:${APPKEY}@${MACHINE}/${destdir} The error message was: BackendException: B2 backend requires B2 Python APIs (pip install b2) The issue is due to a complete rewrite of the Backblaze backend which happened with duplicity-0.7.15. See upstream bug report: https://bugs.launchpad.net/duplicity/+bug/1654756 An ebuild for the python B2 package needs to be added, and added as a dependency to >=app-backup/duplicity-0.7.15.
Created attachment 536152 [details] b2 ebuild This is an ebuild for the b2 package. It's fairly simple, but does stop tests from being packaged correctly (issue raised with upstream), and also renames the b2 executable to b2_bb to avoid clashing with b2 from boost. It does need one out-of-tree ebuild for logfury, a python method-call-logging library. That's also trivial, I can upload that one here too if needed.
Created attachment 657274 [details] b2sdk-1.1.4.ebuild Seeing as people are finding this bug to use b2, here is an updated b2sdk ebuild, current for version 1.1.4. Note that documentation won't build - the final comment in the file lists a missing dependency that is required if the docs USE is enabled, but said package isn't in the tree at the moment.
