From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: backblaze-b2: update to 3.6.0
Date: Wed, 07 Dec 2022 14:42:11 +0100 [thread overview]
Message-ID: <20221207134211.hhSs-5TxE_bNb3av7u1TxrAKpm-ydZCd0favEi-2rTA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40928@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/40928#issuecomment-1340986644
Comment:
I pulled the patch from the corresponding upstream commit.
Fetching from PyPI is sufficient to make `setuptools_scm` work as expected. The GitHub archive is missing some release bits that the package looks for when determining a version.
As for `python3-tqdm`, this is an optional dependency of `python3-b2sdk`. The package is supposed to fall back gracefully to a simple text progress indicator when the package is not installed. We shouldn't add a hard requirement here.
next prev parent reply other threads:[~2022-12-07 13:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:47 [PR PATCH] " ahesford
2022-12-06 16:24 ` [PR PATCH] [Updated] " ahesford
2022-12-06 16:35 ` kartikynwa
2022-12-06 17:21 ` [PR PATCH] [Updated] " ahesford
2022-12-06 17:21 ` ahesford
2022-12-06 17:22 ` ahesford
2022-12-07 5:31 ` kartikynwa
2022-12-07 5:32 ` kartikynwa
2022-12-07 8:41 ` kartikynwa
2022-12-07 8:43 ` kartikynwa
2022-12-07 8:45 ` kartikynwa
2022-12-07 13:37 ` [PR PATCH] [Updated] " ahesford
2022-12-07 13:42 ` ahesford [this message]
2022-12-07 14:21 ` kartikynwa
2022-12-07 14:31 ` kartikynwa
2022-12-07 14:34 ` [PR PATCH] [Updated] " ahesford
2022-12-07 14:35 ` ahesford
2022-12-07 14:44 ` kartikynwa
2022-12-07 14:52 ` [PR PATCH] [Merged]: " ahesford
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=20221207134211.hhSs-5TxE_bNb3av7u1TxrAKpm-ydZCd0favEi-2rTA@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).