Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-pyperclip: update to 1.8.2.
Date: Sat, 23 Jul 2022 16:00:24 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38209@inbox.vuxu.org> (raw)

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

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

https://github.com/icp1994/void-packages python3-pyperclip
https://github.com/void-linux/void-packages/pull/38209

python3-pyperclip: update to 1.8.2.
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### 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/38209.patch is attached

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

From a5c45218cd2136d95a4d1f016aa3afa70ef62210 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 23 Jul 2022 19:29:39 +0530
Subject: [PATCH] python3-pyperclip: update to 1.8.2.

---
 srcpkgs/python3-pyperclip/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-pyperclip/template b/srcpkgs/python3-pyperclip/template
index fe8e5095fa43..16fb6f097e25 100644
--- a/srcpkgs/python3-pyperclip/template
+++ b/srcpkgs/python3-pyperclip/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-pyperclip'
 pkgname=python3-pyperclip
-version=1.8.1
-revision=2
+version=1.8.2
+revision=1
 wrksrc=pyperclip-${version}
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -11,7 +11,11 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="BSD-3-Clause"
 homepage="https://pypi.org/project/pyperclip"
 distfiles="${PYPI_SITE}/p/pyperclip/pyperclip-${version}.tar.gz"
-checksum=9abef1e79ce635eb62309ecae02dfb5a3eb952fa7d6dce09c1aef063f81424d3
+checksum=105254a8b04934f0bc84e9c24eb360a591aaf6535c9def5f29d92af107a9bf57
+
+do_check() {
+	PYTHONPATH="$(cd build/lib* && pwd)" python3 tests/test_pyperclip.py
+}
 
 post_install() {
 	vlicense LICENSE.txt

             reply	other threads:[~2022-07-23 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 14:00 icp1994 [this message]
2022-07-23 16:31 ` [PR REVIEW] " classabbyamp
2022-07-23 16:37 ` icp1994
2022-07-25 14:23 ` ahesford
2022-07-25 16:05 ` icp1994
2022-07-25 16:20 ` classabbyamp
2022-07-25 16:46 ` icp1994
2022-07-25 16:47 ` [PR PATCH] [Updated] " icp1994
2022-07-25 17:16 ` [PR REVIEW] " paper42
2022-07-25 17:22 ` ahesford
2022-07-25 17:26 ` paper42
2022-07-25 17:29 ` icp1994
2022-07-25 17:46 ` ahesford
2022-07-25 18:40 ` [PR PATCH] [Updated] " icp1994
2022-07-25 18:57 ` [PR REVIEW] " icp1994
2022-07-25 19:07 ` paper42
2022-10-24  2:14 ` github-actions
2022-10-24  5:15 ` [PR PATCH] [Updated] " icp1994
2022-10-24  6:36 ` [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-38209@inbox.vuxu.org \
    --to=icp1994@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).