Github messages for voidlinux
 help / color / mirror / Atom feed
From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] peru: update to 1.3.1.
Date: Wed, 03 May 2023 04:08:52 +0200	[thread overview]
Message-ID: <20230503020852.NOMRCWbw1UTXL-JlecoNLyEL3txeowedZHT8kxABjUw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43724@inbox.vuxu.org>

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

There is an updated pull request by atweiden against master on the void-packages repository

https://github.com/atweiden/void-packages peru
https://github.com/void-linux/void-packages/pull/43724

peru: update to 1.3.1.
#### 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-musl

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

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

From 6a4f189f9e06536370bf193acfb79733a85dc26b Mon Sep 17 00:00:00 2001
From: Andy Weidenbaum <atweiden@ioiojo.com>
Date: Wed, 3 May 2023 01:41:58 +0000
Subject: [PATCH] peru: update to 1.3.1.

---
 srcpkgs/peru/template | 26 ++++++++++++++++++++------
 1 file changed, 20 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/peru/template b/srcpkgs/peru/template
index 164984d6f4fc..6b37a010445c 100644
--- a/srcpkgs/peru/template
+++ b/srcpkgs/peru/template
@@ -1,17 +1,31 @@
 # Template file for 'peru'
 pkgname=peru
-version=1.2.0
-revision=5
-build_style=python3-module
-pycompile_module="peru"
-hostmakedepends="python3-setuptools"
+version=1.3.1
+revision=1
+build_style=python3-pep517
+hostmakedepends="hatchling python3-wheel"
 depends="curl git mercurial python3 python3-docopt python3-yaml"
+checkdepends="${depends} python3-pytest rsync subversion"
 short_desc="Tool for fetching code"
 maintainer="Andy Weidenbaum <atweiden@tutanota.de>"
 license="MIT"
 homepage="https://github.com/buildinspace/peru"
 distfiles="https://github.com/buildinspace/peru/archive/${version}.tar.gz>${pkgname}-${version}.tar.gz"
-checksum=fb0fb02639e1c5403c9a6ddfd9719c5ea5ddf69fb440fbcfafe234470645e1dc
+checksum=6a21108f8b0417301d3cd76fa220906cea9d58f95208b70191282972f8bb8ff9
+
+do_check() {
+	local skiptests
+
+	skiptests+=" test_curl_plugin_fetch or"
+	skiptests+=" test_curl_plugin_fetch_archives or"
+	skiptests+=" test_curl_plugin_reup or"
+	skiptests+=" test_git_plugin_with_relative_submodule or"
+	skiptests+=" test_git_plugin_with_submodule or"
+	skiptests+=" test_plugin_fetch or"
+	skiptests+=" test_plugin_get_reup_fields"
+
+	PYTHONPATH="$(cd tests && pwd)" python3 -m pytest -k "not (${skiptests})"
+}
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2023-05-03  2:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  1:43 [PR PATCH] " atweiden
2023-05-03  2:08 ` atweiden [this message]
2023-06-09  9:21 ` [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=20230503020852.NOMRCWbw1UTXL-JlecoNLyEL3txeowedZHT8kxABjUw@z \
    --to=atweiden@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).