Package Details: python-b2sdk 1.13.0-1

Git Clone URL: (read-only, click to copy)
Package Base: python-b2sdk
Description: Python library to access B2 cloud storage.
Upstream URL:
Licenses: MIT
Submitter: 2bluesc
Maintainer: 2bluesc
Last Packager: 2bluesc
Votes: 3
Popularity: 0.053870
First Submitted: 2019-05-04 06:17
Last Updated: 2021-12-07 14:52

Latest Comments

1 2 Next › Last »

samhh commented on 2021-07-13 11:06

@mys_721tx I wonder if that's why Duplicity doesn't work with B2 any more for me..?

mys_721tx commented on 2021-07-03 09:39

community/python-setuptools-scm has upgraded to 6.0.1-1, which breaks the package.

toddejohnson commented on 2021-06-30 16:19

For chroot build it needs makedepends python-pip too. Thank you for maintaining this PKGBUILD!

Kage-Yami commented on 2021-04-04 17:32

Yay, I was helpful. :D That seems to have done the trick for me, my build is now passing (green tick!):

2bluesc commented on 2021-04-04 17:29

@Kage-Yami you're exactly right, I missed that and am able to re-produce your issue. Thanks for providing more details.

I updated it to install python-setuptools-scm. Can you confirm v1.5.0-4 works for you?

Kage-Yami commented on 2021-04-04 17:16

I have very little Python experience/knowledge, but from what I can tell, is mandating that setuptools_scm is < 6.0 (, and so is installing a compatible version via pip; if pip is missing, it obviously results in an error:

subprocess.CalledProcessError: Command '['/usr/sbin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpr6b16ald', '--quiet', 'setuptools_scm<6.0']' returned non-zero exit status 1.

Note that I'm not running any Python scripts at all; aurtils is a collection of purely bash scripts, so the only presence of Python is the build script for this package itself.

Regarding the base image missing pip... pip is not part of base-devel, therefore any package that requires it to be installed for building must specify it as part of makedepends.

Was your pip-less test a build test, or a usage test? (It's unclear from your sentence, and the provided test case suggests the latter, which is irrelevant for the issue at hand...)

Note that I haven't yet tried building it myself manually, so I understand if you don't want to spend time on this; I'm just responding to what you've said, which doesn't make much sense to me.

2bluesc commented on 2021-04-04 16:59

@kage-yami sounds like the base image or the helper util is missing the pip dependency and that you're triggering it by running any python script.

Try running python -c 'print("hello")'

Kage-Yami commented on 2021-04-04 16:47

Ah ok - in my case, it's a shell script running in GitLab CI, building with aurutils in a Docker container based on archlinux:base-devel. So I perfectly understand if you don't want to dive into that (especially given I'm using an AUR helper). :)

If the logs alone reveal anything:

2bluesc commented on 2021-04-04 16:42

I added python-setuptools it's required to build the package with and was a bug to not be included. Fixed it by adding makedepends.

Pip isn't mentioned anywhere in this package other then documentation and comments. I don't see how's it used. I suspect there's a broken Python user config causing these pip errors.

I tested it on my system with python-pip uninstalled and it works correctly as does backblaze-b2.

The following test case showing b2sdk imports successfully (nobody has told me how they are triggering this issue, so I'm guessing), prints the expected version + file path and fails to import pip as it's not installed.

$ python3 -c 'import b2sdk; print(b2sdk.__file__, b2sdk.__version__ ); import pip'
/usr/lib/python3.9/site-packages/b2sdk/ 1.5.0
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'pip'
$ backblaze-b2 version
b2 command line tool, version 2.3.0

Please let me know in detail how you're triggering this pip bug and I can look in to it. I suspect it's a user configuration problem, can perhaps look here: and checkout the environment variables + config paths.

Kage-Yami commented on 2021-04-04 16:09

I'm not sure if the addition of python-setuptools in 1.5.0-2 was supposed to alleviate the pip issue, but it doesn't seem to do so for me; I'm still getting:

/usr/sbin/python: No module named pip

Looking at python-setuptools, python-pip is only a check dependency, not a general dependency.