Package Details: backblaze-b2 3.5.0-2

Git Clone URL: (read-only, click to copy)
Package Base: backblaze-b2
Description: Backblaze B2 Command Line Client
Upstream URL:
Keywords: archive backblaze backup cloud storage
Licenses: MIT
Submitter: 2bluesc
Maintainer: 2bluesc
Last Packager: 2bluesc
Votes: 23
Popularity: 0.163745
First Submitted: 2015-10-29 06:31 (UTC)
Last Updated: 2022-10-18 16:10 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

Archist commented on 2022-10-09 22:42 (UTC) (edited on 2022-10-09 22:53 (UTC) by Archist)

The python-tabulate package in arch was updated to version 0.9.0 on October 6th, but the upstream backblaze repo is still pointing to version 0.8.10, causing this program to fail on import.

Traceback (most recent call last):)
  File "/usr/lib/python3.10/site-packages/pkg_resources/", line 581, in _build_master)
  File "/usr/lib/python3.10/site-packages/pkg_resources/", line 909, in require)
    needed = self.resolve(parse_requirements(requirements)))
  File "/usr/lib/python3.10/site-packages/pkg_resources/", line 800, in resolve)
    raise VersionConflict(dist, req).with_context(dependent_req))
pkg_resources.ContextualVersionConflict: (tabulate 0.9.0 (/usr/lib/python3.10/site-packages), Requirement.parse('tabulate==0.8.10'), {'b2'}))

There is an open PR on the upstream to bump the version.

Artemis commented on 2022-03-17 10:31 (UTC) (edited on 2022-03-17 10:32 (UTC) by Artemis)

The following patch updates the version to 3.2.1 and also points the download to github:

diff --git a/PKGBUILD b/PKGBUILD
index c27d11c..cf3b7d1 100644
@@ -2,7 +2,7 @@

 pkgdesc='Backblaze B2 Command Line Client'
@@ -23,8 +23,8 @@ makedepends=('python-pip'


 build() {
     cd ${srcdir}/${_pkgname}-${pkgver}

Hoek commented on 2022-01-15 23:20 (UTC)

@2bluesc thank you, that helped!

2bluesc commented on 2022-01-15 16:44 (UTC)

@Hoek you probably need to rebuild your AUR packages built against Python 3.9 after installing 3.10:

pacman -Qoq /usr/lib/python3.9
yay -S $(pacman -Qoq /usr/lib/python3.9) --answerclean All

Or something similar.

Hoek commented on 2021-12-31 14:30 (UTC)

Current version fails to run:

Traceback (most recent call last):
  File "/bin/backblaze-b2", line 33, in <module>
    sys.exit(load_entry_point('b2==3.1.0', 'console_scripts', 'b2')())
  File "/bin/backblaze-b2", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.10/importlib/metadata/", line 919, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.10/importlib/metadata/", line 518, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for b2

Kage-Yami commented on 2021-07-08 10:29 (UTC) (edited on 2021-07-08 10:33 (UTC) by Kage-Yami)

Looks like while the last issue I reported has been resolved, we've had a regression with the setuptools_scm dependency - this is back to failing to build in environments without pip, similar to what was happening back in April, as it looks like the requirement of <6.0 was removed in the last AUR update, without also patching out the requirement from the source code.

samhh commented on 2021-07-03 11:19 (UTC)

Is anyone else finding that as of 2.5.0 of this package Duplicity isn't working with Backblaze?

BackendException: Could not initialise backend: No module named 'b2sdk.download_dest'

toddejohnson commented on 2021-06-30 16:21 (UTC)

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

Hoek commented on 2021-06-23 21:16 (UTC)

Today's python-setuptools-scm 6.0.1 release broke this package:

error: could not find all required packages:
    python-setuptools-scm<6.0 (wanted by: backblaze-b2)

Kage-Yami commented on 2021-06-14 06:54 (UTC)

Hi again, looks like the packaging for this might be broken again (at least in some scenarios)...

My builds for this have been working fine up until two days ago (12-Jun). However, starting yesterday, running the package has started to fail (so not sure if the builds will still fail or not, as my CI pipeline doesn't get that far).

The relevant parts of the error (at least as far as I can glean) is:

pkg_resources.ContextualVersionConflict: (docutils 0.17 (/usr/lib/python3.9/site-packages), Requirement.parse('docutils==0.16'), {'b2'})
 -- snip --
pkg_resources.DistributionNotFound: The 'docutils==0.16' distribution was not found and is required by b2

Full error can be seen here:

Looking in the requirements.txt for the upstream repository, it contains docutils==0.16, but this package has listed docutils>=0.16 as a dependency, allowing 0.17 to be installed instead.

So as I understand it, the solution is to switch this package to depend on docutils==0.16 instead.

Looks like Arch only started packaging 0.17 two days ago, which would explain the timing of this issue (the docutils upstream had released 0.17 in April)