Pin b2sdk to version 1.14.1 in the virtualenv also

We install b2sdk in two places: Once globally for duplicity (see 9d8fdef9915127f016eb6424322a149cdff25d7 for #2125) and once in a virtualenv used by our control panel. The latter wasn't pinned when the former was but should be to fix new Python compatibility issues. Anyone who updated Python packages recently (so anyone who upgraded Mail-in-a-Box) started encountering these issues. Fixes #2131. See https://discourse.mailinabox.email/t/backblaze-b2-backup-not-working-since-v57/9231.
mail-in-a-box · Jun 18, 2022 · d829d74 · d829d74
1 parent 2aca421
commit d829d74
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/setup/management.sh b/setup/management.sh
@@ -51,7 +51,8 @@ hide_output $venv/bin/pip install --upgrade \
 	rtyaml "email_validator>=1.0.0" "exclusiveprocess" \
 	flask dnspython python-dateutil expiringdict \
 	qrcode[pil] pyotp \
-	"idna>=2.0.0" "cryptography==2.2.2" boto psutil postfix-mta-sts-resolver b2sdk
+	"idna>=2.0.0" "cryptography==2.2.2" psutil postfix-mta-sts-resolver \
+	b2sdk==1.14.1 boto
 
 # CONFIGURATION