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.0.
Date: Sun, 27 Feb 2022 08:26:57 +0100	[thread overview]
Message-ID: <20220227072657.LtLZDGho6y4S4ZV0wxL3daTiQFaUQ3lffJYBO5P-Ny0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35871@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 472 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/35871

peru: update to 1.3.0.
Mercurial is an optional dependency (see: https://github.com/buildinspace/peru/pull/224).

#### Testing the changes
- I tested the changes in this PR: **YES**

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

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

From 54906136392eab98f4c1199d9bef2af5b89896e3 Mon Sep 17 00:00:00 2001
From: Andy Weidenbaum <atweiden@ioiojo.com>
Date: Sun, 27 Feb 2022 18:04:55 +1100
Subject: [PATCH] peru: update to 1.3.0.

---
 srcpkgs/peru/template | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/peru/template b/srcpkgs/peru/template
index 7f77496c6fa4..5d209df04205 100644
--- a/srcpkgs/peru/template
+++ b/srcpkgs/peru/template
@@ -1,17 +1,21 @@
 # Template file for 'peru'
 pkgname=peru
-version=1.2.0
-revision=4
+version=1.3.0
+revision=1
 build_style=python3-module
-pycompile_module="peru"
 hostmakedepends="python3-setuptools"
-depends="curl git mercurial python3 python3-docopt python3-yaml"
+depends="curl git python3 python3-docopt python3-yaml"
+checkdepends="${depends} flake8 python3-pip python3-wheel"
 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=ba21eb65c62c1b823ece2a42375fe80d65fbc6130606e2d6850b7746530018f6
+
+do_check() {
+	python3 test.py
+}
 
 post_install() {
 	vlicense LICENSE

  parent reply	other threads:[~2022-02-27  7:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27  7:13 [PR PATCH] " atweiden
2022-02-27  7:19 ` [PR PATCH] [Updated] " atweiden
2022-02-27  7:26 ` atweiden [this message]
2022-02-27  7:31 ` atweiden
2022-02-28 11:57 ` tibequadorian
2022-02-28 20:31 ` atweiden
2022-03-02  0:26 ` tibequadorian
2022-03-02  0:52 ` tibequadorian
2022-03-02  4:28 ` atweiden
2022-06-26  2:17 ` github-actions
2022-07-11  2:13 ` [PR PATCH] [Closed]: " github-actions

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=20220227072657.LtLZDGho6y4S4ZV0wxL3daTiQFaUQ3lffJYBO5P-Ny0@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).