Github messages for voidlinux
 help / color / mirror / Atom feed
From: pfpulux <pfpulux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-itsdangerous: update to 2.1.2.
Date: Fri, 25 Mar 2022 16:58:12 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36336@inbox.vuxu.org> (raw)

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

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

https://github.com/pfpulux/void-packages python3-itsdangerous
https://github.com/void-linux/void-packages/pull/36336

python3-itsdangerous: update to 2.1.2.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/36336.patch is attached

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

From 9d4247441b16004a86f207f805081ff7a1d67024 Mon Sep 17 00:00:00 2001
From: Pulux <pulux@pf4sh.de>
Date: Fri, 25 Mar 2022 16:55:44 +0100
Subject: [PATCH] python3-itsdangerous: update to 2.1.2.

---
 srcpkgs/python3-itsdangerous/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-itsdangerous/template b/srcpkgs/python3-itsdangerous/template
index 6fa31a0342fd..b770f01eef0c 100644
--- a/srcpkgs/python3-itsdangerous/template
+++ b/srcpkgs/python3-itsdangerous/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-itsdangerous'
 pkgname=python3-itsdangerous
-version=2.0.1
-revision=2
+version=2.1.2
+revision=1
 wrksrc="${pkgname#*-}-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -12,7 +12,7 @@ maintainer="Markus Berger <pulux@pf4sh.de>"
 license="BSD-3-Clause"
 homepage="http://github.com/mitsuhiko/itsdangerous"
 distfiles="${PYPI_SITE}/i/itsdangerous/itsdangerous-${version}.tar.gz"
-checksum=9e724d68fc22902a1435351f84c3fb8623f303fffcc566a4cb952df8c572cff0
+checksum=5dbbc68b317e5e42f327f9021763545dc3fc3bfe22e6deb96aaf1fc38874156a
 
 post_install() {
 	vlicense LICENSE.rst

             reply	other threads:[~2022-03-25 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 15:58 pfpulux [this message]
2022-04-07 14:08 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36336@inbox.vuxu.org \
    --to=pfpulux@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).