Github messages for voidlinux
 help / color / mirror / Atom feed
From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-rapidfuzz: update to 3.9.5
Date: Tue, 30 Jul 2024 15:36:03 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51544@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

There is a new pull request by chrysos349 against master on the void-packages repository

https://github.com/chrysos349/void-packages python3-rapidfuzz
https://github.com/void-linux/void-packages/pull/51544

python3-rapidfuzz: update to 3.9.5
#### 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)

A patch file from https://github.com/void-linux/void-packages/pull/51544.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-rapidfuzz-51544.patch --]
[-- Type: text/x-diff, Size: 1935 bytes --]

From f749213761226111acd158b9fee29b4921224804 Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Tue, 30 Jul 2024 16:29:48 +0300
Subject: [PATCH] python3-rapidfuzz: update to 3.9.5

---
 .../patches/scikit-build-ver.patch                  | 13 -------------
 srcpkgs/python3-rapidfuzz/template                  |  4 ++--
 2 files changed, 2 insertions(+), 15 deletions(-)
 delete mode 100644 srcpkgs/python3-rapidfuzz/patches/scikit-build-ver.patch

diff --git a/srcpkgs/python3-rapidfuzz/patches/scikit-build-ver.patch b/srcpkgs/python3-rapidfuzz/patches/scikit-build-ver.patch
deleted file mode 100644
index 06ee964aa47775..00000000000000
--- a/srcpkgs/python3-rapidfuzz/patches/scikit-build-ver.patch
+++ /dev/null
@@ -1,13 +0,0 @@
-diff --git a/pyproject.toml b/pyproject.toml
-index 26c32df3d..72a570c94 100644
---- a/pyproject.toml
-+++ b/pyproject.toml
-@@ -1,7 +1,7 @@
- [build-system]
- requires = [
-     "setuptools>=42",
--    "scikit-build~=0.17.0"
-+    "scikit-build>=0.17.0"
- ]
- build-backend = "backend"
- backend-path = ["_custom_build"]
diff --git a/srcpkgs/python3-rapidfuzz/template b/srcpkgs/python3-rapidfuzz/template
index 3b82c779d038dd..bf6a0e706ace2e 100644
--- a/srcpkgs/python3-rapidfuzz/template
+++ b/srcpkgs/python3-rapidfuzz/template
@@ -1,6 +1,6 @@
 # Template file for 'python3-rapidfuzz'
 pkgname=python3-rapidfuzz
-version=3.9.4
+version=3.9.5
 revision=1
 build_style=python3-pep517
 hostmakedepends="cmake python3-scikit-build"
@@ -13,7 +13,7 @@ license="MIT"
 homepage="https://github.com/maxbachmann/rapidfuzz"
 changelog="https://github.com/rapidfuzz/RapidFuzz/releases"
 distfiles="${PYPI_SITE}/r/rapidfuzz/rapidfuzz-${version}.tar.gz"
-checksum=366bf8947b84e37f2f4cf31aaf5f37c39f620d8c0eddb8b633e6ba0129ca4a0a
+checksum=257f2406a671371bafd99a2a2c57f991783446bc2176b93a83d1d833e35d36df
 
 export CMAKE_ARGS="-DPython_INCLUDE_DIR:PATH=${XBPS_CROSS_BASE}/${py3_inc}"
 

             reply	other threads:[~2024-07-30 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 13:36 chrysos349 [this message]
2024-07-31 21:45 ` [PR PATCH] [Closed]: " classabbyamp

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51544@inbox.vuxu.org \
    --to=chrysos349@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).