From: sww1235 <sww1235@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Backblaze-b2: Patch TQDM version
Date: Sat, 25 Nov 2023 23:11:45 +0100 [thread overview]
Message-ID: <20231125221145.fEfJlrQ6KT1-MF4FHYawkBDKJpfUsT6e8r1urHUaaM0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47400@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
There is an updated pull request by sww1235 against master on the void-packages repository
https://github.com/sww1235/void-packages backblaze-fixes
https://github.com/void-linux/void-packages/pull/47400
Backblaze-b2: Patch TQDM version
Allows package to build with newer version of tqdm in void-packages. Upstream has a dependabot pull that passed all their tests, but is not merged yet.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64 glibc)
Closes #47348
A patch file from https://github.com/void-linux/void-packages/pull/47400.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-backblaze-fixes-47400.patch --]
[-- Type: text/x-diff, Size: 1442 bytes --]
From 6521537df72f410794183d3ae63a1464cef0866e Mon Sep 17 00:00:00 2001
From: Stephen Walker-Weinshenker <sww1235@sww1235.net>
Date: Sat, 25 Nov 2023 11:55:27 -0700
Subject: [PATCH] Patching tqdm requirement
Allows package to build with newer version in void-packages
---
srcpkgs/backblaze-b2/patches/tqdm_ver.patch | 10 ++++++++++
srcpkgs/backblaze-b2/template | 2 +-
2 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/backblaze-b2/patches/tqdm_ver.patch
diff --git a/srcpkgs/backblaze-b2/patches/tqdm_ver.patch b/srcpkgs/backblaze-b2/patches/tqdm_ver.patch
new file mode 100644
index 0000000000000..35e7701c9eef2
--- /dev/null
+++ b/srcpkgs/backblaze-b2/patches/tqdm_ver.patch
@@ -0,0 +1,10 @@
+Upstream builds with the newer version of tqdm, but upstream hasn't updated their requirements.txt
+
+--- a/requirements.txt
++++ b/requirements.txt
+@@ -7,4 +7,4 @@
+ phx-class-registry~=4.0
+ rst2ansi==0.1.5
+ tabulate==0.9.0
+-tqdm~=4.65.0
++tqdm>=4.65.0
diff --git a/srcpkgs/backblaze-b2/template b/srcpkgs/backblaze-b2/template
index aa42641f0f336..ddb5895545c37 100644
--- a/srcpkgs/backblaze-b2/template
+++ b/srcpkgs/backblaze-b2/template
@@ -1,7 +1,7 @@
# Template file for 'backblaze-b2'
pkgname=backblaze-b2
version=3.11.0
-revision=2
+revision=3
build_style=python3-module
hostmakedepends="python3-setuptools_scm python3-wheel"
depends="python3-Arrow python3-b2sdk python3-docutils
next prev parent reply other threads:[~2023-11-25 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 19:00 [PR PATCH] " sww1235
2023-11-25 19:03 ` sww1235
2023-11-25 19:12 ` sww1235
2023-11-25 21:43 ` [PR REVIEW] " ahesford
2023-11-25 22:10 ` sww1235
2023-11-25 22:11 ` sww1235 [this message]
2023-11-25 23:41 ` ahesford
2023-11-26 4:01 ` [PR PATCH] [Updated] " sww1235
2023-11-26 4:01 ` sww1235
2023-11-26 4:03 ` sww1235
2023-11-26 4:07 ` [PR PATCH] [Merged]: " ahesford
2023-11-26 4:09 ` sww1235
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=20231125221145.fEfJlrQ6KT1-MF4FHYawkBDKJpfUsT6e8r1urHUaaM0@z \
--to=sww1235@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).