From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Backblaze B2 broken with update of TQDM
Date: Sun, 26 Nov 2023 05:07:24 +0100 [thread overview]
Message-ID: <20231126040724.yH87SJmN-83OzhSx2xgSrVcSGLmTcdnJA0yKR3zlWC8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47348@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Closed issue by sww1235 on void-packages repository
https://github.com/void-linux/void-packages/issues/47348
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.9_1 x86_64 GenuineIntel uptodate rrrrmmnFFFFFFFF
### Package(s) Affected
backblaze-b2-3.11.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Expected package to launch and show help
MWE: run `backblaze-b2` in your shell.
### Actual behaviour
The package binary does not run and spits out an ugly python error message ending in `pkg_resources.DistributionNotFound: The 'tqdm~=4.65.0' distribution was not found and is required by b2`
There was also a previous error that the package required `argcomplete` which was fixed by manually installing `python3-argcomplete`
### Steps to reproduce
1. Update system
2. Install `backblaze-b2` and dependancies
3. fail to run `backblaze-b2` on `argcomplete` error
4. manually install `argcomplete`
5. fail to run `backblaze-b2`on `tqdm` error
prev parent reply other threads:[~2023-11-26 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:58 [ISSUE] " sww1235
2023-11-22 4:01 ` sww1235
2023-11-22 4:06 ` sww1235
2023-11-26 4:07 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231126040724.yH87SJmN-83OzhSx2xgSrVcSGLmTcdnJA0yKR3zlWC8@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).