From: littlewing7 <littlewing7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libvterm: update to 0.3.1
Date: Fri, 28 Apr 2023 18:48:12 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43658@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
There is a new pull request by littlewing7 against master on the void-packages repository
https://github.com/littlewing7/void-packages libvterm_0.3.1
https://github.com/void-linux/void-packages/pull/43658
libvterm: update to 0.3.1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
- I built this PR locally for these architectures:
- aarch64
- aarch64-musl
- armv7l
- armv6l
- armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/43658.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libvterm_0.3.1-43658.patch --]
[-- Type: text/x-diff, Size: 1055 bytes --]
From aa1537ed467eb5da8983b944d875d93f01289e0c Mon Sep 17 00:00:00 2001
From: Massimo Manzato <massimo.manzato@gmail.com>
Date: Fri, 28 Apr 2023 17:39:42 +0200
Subject: [PATCH] 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
next reply other threads:[~2023-04-28 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 16:48 littlewing7 [this message]
2023-04-30 1:46 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43658@inbox.vuxu.org \
--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).