From: Barbaross93 <Barbaross93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vit: update to 2.2.0
Date: Mon, 18 Apr 2022 15:56:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36754@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
There is a new pull request by Barbaross93 against master on the void-packages repository
https://github.com/Barbaross93/void-packages vit
https://github.com/void-linux/void-packages/pull/36754
vit: update to 2.2.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!-- 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 (x86-64)
A patch file from https://github.com/void-linux/void-packages/pull/36754.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vit-36754.patch --]
[-- Type: text/x-diff, Size: 964 bytes --]
From 58694c91eb2484be1d764f46eb319c84df10c2e0 Mon Sep 17 00:00:00 2001
From: Barbaross <cullenrss@gmail.com>
Date: Mon, 18 Apr 2022 09:54:39 -0400
Subject: [PATCH] vit: update to 2.2.0
---
srcpkgs/vit/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/vit/template b/srcpkgs/vit/template
index 173648d69b95..55ff23e87cb4 100644
--- a/srcpkgs/vit/template
+++ b/srcpkgs/vit/template
@@ -1,6 +1,6 @@
# Template file for 'vit'
pkgname=vit
-version=2.1.0
+version=2.2.0
revision=1
build_style=python3-module
hostmakedepends="python3-setuptools"
@@ -11,7 +11,7 @@ maintainer="Cullen Ross <cullenrss@gmail.com>"
license="MIT"
homepage="https://github.com/vit-project/vit"
distfiles="${PYPI_SITE}/v/vit/vit-${version}.tar.gz"
-checksum=fd34f0b827953dfdecdc39f8416d41c50c24576c33a512a047a71c1263eb3e0f
+checksum=e866c8739822b9e73152ab30c9a009c3aef947533c06f7a5cb244d15c4ea296f
do_check() {
TERM=linux python3 -m pytest
next reply other threads:[~2022-04-18 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 13:56 Barbaross93 [this message]
2022-04-18 18:15 ` [PR PATCH] [Updated] " Barbaross93
2022-04-18 18:21 ` Barbaross93
2022-04-18 18:23 ` [PR PATCH] [Updated] " Barbaross93
2022-04-18 18:24 ` Barbaross93
2022-04-18 20:56 ` paper42
2022-04-18 21:06 ` [PR PATCH] [Merged]: " paper42
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-36754@inbox.vuxu.org \
--to=barbaross93@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).