Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tio: update to 1.47.
Date: Sat, 30 Jul 2022 17:41:45 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38373@inbox.vuxu.org> (raw)

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

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

https://github.com/0x5c/void-packages update-tio
https://github.com/void-linux/void-packages/pull/38373

tio: update to 1.47.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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
-->


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

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

From c9a76906e0297f284ce4dfd343bf5959ac5a2a6e Mon Sep 17 00:00:00 2001
From: 0x5c <dev@0x5c.io>
Date: Sat, 30 Jul 2022 11:37:14 -0400
Subject: [PATCH] tio: update to 1.47.

---
 srcpkgs/tio/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/tio/template b/srcpkgs/tio/template
index 58cf3069371d..6e69f06b33af 100644
--- a/srcpkgs/tio/template
+++ b/srcpkgs/tio/template
@@ -1,6 +1,6 @@
 # Template file for 'tio'
 pkgname=tio
-version=1.46
+version=1.47
 revision=1
 build_style=meson
 hostmakedepends="pkg-config"
@@ -11,8 +11,9 @@ license="GPL-2.0-or-later"
 homepage="https://github.com/tio/tio"
 changelog="https://github.com/tio/tio/raw/master/NEWS"
 distfiles="https://github.com/tio/tio/archive/refs/tags/v${version}.tar.gz"
-checksum=7d08d89e862a326b687b7fc73d9b266c715d1c68cd4e46f1361e5a98994c5941
+checksum=d1cad2c8482f656d4f392e34bd7acae8e14e44c10ff8f98379d6415919f8ab31
 
 post_install() {
 	vcompletion "build/src/bash-completion/tio" bash tio
+	vsconf "example/tiorc"
 }

             reply	other threads:[~2022-07-30 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 15:41 0x5c [this message]
2022-07-31  6:23 ` [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-38373@inbox.vuxu.org \
    --to=0x5c@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).