From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-Arrow: update to 1.2.3
Date: Sun, 25 Sep 2022 17:15:04 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39465@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages arrow
https://github.com/void-linux/void-packages/pull/39465
python3-Arrow: update to 1.2.3
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/39465.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-arrow-39465.patch --]
[-- Type: text/x-diff, Size: 1386 bytes --]
From f521a0a66573ad56fb8e31c1d80ef7351398fd57 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sun, 25 Sep 2022 17:11:59 +0200
Subject: [PATCH] python3-Arrow: update to 1.2.3
---
srcpkgs/python3-Arrow/template | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/python3-Arrow/template b/srcpkgs/python3-Arrow/template
index 3330d66e08e8..fe1334639f09 100644
--- a/srcpkgs/python3-Arrow/template
+++ b/srcpkgs/python3-Arrow/template
@@ -1,14 +1,17 @@
# Template file for 'python3-Arrow'
pkgname=python3-Arrow
-version=0.15.5
-revision=4
+version=1.2.3
+revision=1
wrksrc="arrow-${version}"
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-dateutil"
+checkdepends="${depends} python3-pytest python3-pytest-cov python3-pytest-mock
+ python3-pytz python3-simplejson"
short_desc="Better dates & times for Python (Python3)"
maintainer="Andrea Brancaleoni <miwaxe@gmail.com>"
license="Apache-2.0"
-homepage="https://github.com/crsmithdev/arrow"
+homepage="https://github.com/arrow-py/arrow"
+changelog="https://raw.githubusercontent.com/arrow-py/arrow/master/CHANGELOG.rst"
distfiles="${PYPI_SITE}/a/arrow/arrow-${version}.tar.gz"
-checksum=5390e464e2c5f76971b60ffa7ee29c598c7501a294bc9f5e6dadcb251a5d027b
+checksum=3934b30ca1b9f292376d9db15b19446088d12ec58629bc3f0da28fd55fb633a1
next reply other threads:[~2022-09-25 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:15 tranzystorek-io [this message]
2022-09-26 13:08 ` [PR PATCH] [Merged]: " 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-39465@inbox.vuxu.org \
--to=tranzystorek-io@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).