Github messages for voidlinux
 help / color / mirror / Atom feed
From: littlewing7 <littlewing7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libtickit and libvterm update  
Date: Thu, 20 Apr 2023 08:40:24 +0200	[thread overview]
Message-ID: <20230420064024.mGaTrs4vNYCqtqe6wi5p9ME3bMbpnQTNKByfmBIUKOc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43532@inbox.vuxu.org>

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

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

https://github.com/littlewing7/void-packages libtickit_maintenance
https://github.com/void-linux/void-packages/pull/43532

libtickit and libvterm update  
<!-- 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 [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:
  - x86_64-musl



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

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

From 5091dc86d2491cdcf4810fef202230358b40e46b Mon Sep 17 00:00:00 2001
From: Massimo Manzato <massimo.manzato@gmail.com>
Date: Tue, 18 Apr 2023 10:59:01 +0200
Subject: [PATCH 1/2] libtickit: update to 0.4.3.

---
 srcpkgs/libtickit/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libtickit/template b/srcpkgs/libtickit/template
index 6b2d82cfd0ae..cba78eaf976e 100644
--- a/srcpkgs/libtickit/template
+++ b/srcpkgs/libtickit/template
@@ -1,6 +1,6 @@
 # Template file for 'libtickit'
 pkgname=libtickit
-version=0.4.1
+version=0.4.3
 revision=1
 build_style=gnu-makefile
 make_build_args="LIBTOOL=${XBPS_CROSS_BASE}/usr/bin/libtool"
@@ -14,7 +14,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="http://www.leonerd.org.uk/code/libtickit/"
 distfiles="http://www.leonerd.org.uk/code/libtickit/libtickit-${version}.tar.gz"
-checksum=48b72a12548da23f32384ddf0f8d727bc27515f36a74d2f4d4f0bbbb562a2665
+checksum=a830588fa1f4c99d548c11e6df50281c23dfa01f75e2ab95151f02715db6bd63
 
 post_install() {
 	vlicense LICENSE

From c7bee583283211a67ac488e8f96a02bf26c7e3c9 Mon Sep 17 00:00:00 2001
From: Massimo Manzato <massimo.manzato@gmail.com>
Date: Tue, 18 Apr 2023 12:56:58 +0200
Subject: [PATCH 2/2] libvterm: update to 0.3.1.

---
 srcpkgs/libvterm/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libvterm/template b/srcpkgs/libvterm/template
index ef8a8c655f7e..a7a7042e0e23 100644
--- a/srcpkgs/libvterm/template
+++ b/srcpkgs/libvterm/template
@@ -1,6 +1,6 @@
 # Template file for 'libvterm'
 pkgname=libvterm
-version=0.3
+version=0.3.1
 revision=1
 build_style=gnu-makefile
 make_install_target="install-lib install-inc"
@@ -10,7 +10,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://www.leonerd.org.uk/code/libvterm"
 distfiles="https://www.leonerd.org.uk/code/libvterm/libvterm-${version}.tar.gz"
-checksum=61eb0d6628c52bdf02900dfd4468aa86a1a7125228bab8a67328981887483358
+checksum=25a8ad9c15485368dfd0a8a9dca1aec8fea5c27da3fa74ec518d5d3787f0c397
 
 post_extract() {
 	if [ "$CROSS_BUILD" ]; then

  parent reply	other threads:[~2023-04-20  6:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 22:05 [PR PATCH] " littlewing7
2023-04-19 22:09 ` [PR PATCH] [Updated] " littlewing7
2023-04-19 22:14 ` mhmdanas
2023-04-19 22:15 ` mhmdanas
2023-04-20  6:40 ` littlewing7 [this message]
2023-04-20 10:17 ` littlewing7
2023-04-20 11:59 ` [PR PATCH] [Updated] " abenson
2023-04-20 12:04 ` abenson
2023-04-20 12:06 ` abenson
2023-04-20 12:07 ` abenson
2023-04-20 13:51 ` littlewing7
2023-04-26 13:59 ` littlewing7
2023-04-26 15:26 ` abenson
2023-04-26 20:23 ` [PR REVIEW] " mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 20:23 ` mhmdanas
2023-04-26 22:04 ` littlewing7
2023-04-27 11:36 ` abenson
2023-04-27 11:39 ` littlewing7
2023-04-27 20:32 ` mhmdanas
2023-04-28  7:09 ` littlewing7
2023-04-28  7:10 ` littlewing7
2023-04-28  8:43 ` littlewing7
2023-05-03 16:44 ` [PR PATCH] [Updated] " littlewing7
2023-05-03 16:55 ` littlewing7
2023-05-03 17:03 ` [PR PATCH] [Updated] libtickit update littlewing7
2023-05-03 17:05 ` littlewing7
2023-05-03 17:16 ` littlewing7
2023-05-03 17:19 ` littlewing7
2023-05-03 17:27 ` [PR PATCH] [Closed]: " abenson

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=20230420064024.mGaTrs4vNYCqtqe6wi5p9ME3bMbpnQTNKByfmBIUKOc@z \
    --to=littlewing7@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).