[SOLVED] Duplicity B2 backend python dep b2sdk not available

[Punchcutter]

Hi.... I would like to use duplicity for backup to Backblaze B2, which I am just beginning to experiment with. This must be a rare thing for Gentoo (at least power)users because it is broken, seemingly for quite a few years, and this is because a dependency is missing: b2sdk, which does not seem to be packaged for portage.

I found this bug report, which apparently contains an ebuild offered by the reporter to fix the problem.

But it also seems that I could install pip, which is not currently there, and install the dependency library that way, directly into my system python.

What would be the best way to solve this? I'm sympathetic to the idea that it might be bad practice to "contaminate" one's system python with libraries required for a single user app, but I'm not sure how to go about setting up a separate python just for this purpose, or if I would even want to. OTOH, I'm not familiar/comfortable with the mechanism for taking a random ebuild which is not part of the portage tree and building it into my system, or if it might be bad security practice to do so with an ebuild of uncertain origin.

Any advice much appreciated.

[Phoenix591]

You're in luck: a more recent ebuild is already in Guru (like Arch's AUR)

To easily add the Guru repository

[Genone]

Well, pip supports installing packages into a virtual environment instead of the system installation, so that sounds like the easiest option if you don't want to setup a local ebuild repository (requires a little effort to setup though).
The ebuild in the bug report isn't anything special, basically does the same thing as pip (doesn't contain any actual code, simply uses the standard eclass for python packages). Don't know anything about the involved packages themselves though.

[Punchcutter]

Thanks for the ideas... I decided to go with Guru, and everything's working now. There were a few more things that needed to be done, beyond Phoenix591's instructions:

[Hu]

Testing versions of packages are allowed to depend on other testing versions. When you tried to enable b2sdk testing alone, it had an unsatisfied dependency on logfury testing, so Portage picked the older b2sdk that would accept the stable logfury.