From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vile: update to 9.8y
Date: Wed, 18 Jan 2023 21:18:44 +0100 [thread overview]
Message-ID: <20230118201844.6C1rmL2_VT3-7ZJi-d9_IZALPlJbUkjXBlQJ37jbqpI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41724@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
There is an updated pull request by clyhtsuriva against master on the void-packages repository
https://github.com/clyhtsuriva/void-packages vile-update
https://github.com/void-linux/void-packages/pull/41724
vile: update to 9.8y
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I crossbuilded this PR locally for these architectures:
A patch file from https://github.com/void-linux/void-packages/pull/41724.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vile-update-41724.patch --]
[-- Type: text/x-diff, Size: 1027 bytes --]
From 444d6bc6ee5c3df487fb0c9aabd2a4deddabb524 Mon Sep 17 00:00:00 2001
From: clyhtsuriva <aimeric@adjutor.xyz>
Date: Wed, 18 Jan 2023 21:15:27 +0100
Subject: [PATCH] vile: update to 9.8y
---
srcpkgs/vile/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/vile/template b/srcpkgs/vile/template
index f3b6cbb8c83b..9bac5ba2a238 100644
--- a/srcpkgs/vile/template
+++ b/srcpkgs/vile/template
@@ -1,6 +1,6 @@
# Template file for 'vile'
pkgname=vile
-version=9.8w
+version=9.8y
revision=1
build_style=gnu-configure
configure_args="--disable-stripping"
@@ -11,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only"
homepage="http://invisible-island.net/vile/vile.html"
distfiles="https://invisible-mirror.net/archives/vile/current/vile-${version}.tgz"
-checksum=78253ec3f7ae5f4f9d4799a3c8bc35b85b47d456f2ac172810008a48e4609815
+checksum=1b67f1ef34f5f2075722ab46184bb149735e8538fa912fc07c985c92f78fe381
post_extract() {
sed -i 's/\[\[//g' filters/sh-filt.l
next prev parent reply other threads:[~2023-01-18 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 20:15 [PR PATCH] " clyhtsuriva
2023-01-18 20:18 ` clyhtsuriva [this message]
2023-01-18 20:21 ` [PR PATCH] [Updated] " clyhtsuriva
2023-01-18 22:37 ` clyhtsuriva
2023-04-19 1:54 ` github-actions
2023-05-04 1:51 ` [PR PATCH] [Closed]: " github-actions
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 21:42 [PR PATCH] vile: update to 9.8x clyhtsuriva
2023-01-18 20:01 ` [PR PATCH] [Updated] vile: update to 9.8y clyhtsuriva
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=20230118201844.6C1rmL2_VT3-7ZJi-d9_IZALPlJbUkjXBlQJ37jbqpI@z \
--to=clyhtsuriva@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).