Github messages for voidlinux
 help / color / mirror / Atom feed
From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] vit: update to 2.3.2.
Date: Fri, 01 Dec 2023 17:27:17 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47520@inbox.vuxu.org> (raw)

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

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

https://github.com/m3tav3rse/void-packages vit
https://github.com/void-linux/void-packages/pull/47520

vit: update to 2.3.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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->

Fixes #47410

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

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

From dd4535f2e2d64b1b11a15778f658d3a0e3e2a798 Mon Sep 17 00:00:00 2001
From: mtvrs <mtvrs@tuta.io>
Date: Fri, 1 Dec 2023 17:18:20 +0100
Subject: [PATCH] vit: update to 2.3.2.

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

diff --git a/srcpkgs/vit/template b/srcpkgs/vit/template
index 421ebed948b46..6def6d6c4c6e8 100644
--- a/srcpkgs/vit/template
+++ b/srcpkgs/vit/template
@@ -1,7 +1,7 @@
 # Template file for 'vit'
 pkgname=vit
-version=2.3.0
-revision=2
+version=2.3.2
+revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
 depends="task python3-urwid python3-tasklib"
@@ -11,7 +11,7 @@ maintainer="Cullen Ross <cullen.ross@proton.me>"
 license="MIT"
 homepage="https://github.com/vit-project/vit"
 distfiles="${PYPI_SITE}/v/vit/vit-${version}.tar.gz"
-checksum=f3efd871c607f201251a5d1e0082e5e31e9161dde0df0c6d8b5a3447c76c87c6
+checksum=a837d8e865a70d0e384a1e78d314330f000d108fa62e3a72d9aec6dec7ca233c
 
 do_check() {
 	TERM=linux python3 -m pytest

             reply	other threads:[~2023-12-01 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 16:27 m3tav3rse [this message]
2023-12-02  7:13 ` [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-47520@inbox.vuxu.org \
    --to=m3tav3rse@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).