From: m3tav3rse <m3tav3rse@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] moar: update to 1.16.2.
Date: Sun, 17 Sep 2023 15:12:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46102@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
There is a new pull request by m3tav3rse against master on the void-packages repository
https://github.com/m3tav3rse/void-packages moar
https://github.com/void-linux/void-packages/pull/46102
moar: update to 1.16.2.
<!-- 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 (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/46102.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-moar-46102.patch --]
[-- Type: text/x-diff, Size: 1146 bytes --]
From 8fe864179bf97682c2ae2c2de856c02e7c2946fd Mon Sep 17 00:00:00 2001
From: m3tav3rse <mtvrs@tuta.io>
Date: Sun, 17 Sep 2023 15:10:23 +0200
Subject: [PATCH] moar: update to 1.16.2.
---
srcpkgs/moar/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/moar/template b/srcpkgs/moar/template
index 8994295a4f1ad..dc5c7473b66ac 100644
--- a/srcpkgs/moar/template
+++ b/srcpkgs/moar/template
@@ -1,6 +1,6 @@
# Template file for 'moar'
pkgname=moar
-version=1.16.0
+version=1.16.2
revision=1
build_style=go
go_import_path=github.com/walles/moar
@@ -9,9 +9,9 @@ short_desc="Drop-in replacement for the less pager"
maintainer="Diego Magdaleno <diegomagdaleno@pm.me>"
license="BSD-2-Clause"
homepage="https://github.com/walles/moar"
-changelog="https://github.com/waller/moar/releases"
+changelog="https://github.com/walles/moar/releases"
distfiles="https://github.com/walles/moar/archive/refs/tags/v${version}.tar.gz"
-checksum=39142047aee50f3823bd3223d28ba8133c202deca2c0689402a4606d74c63251
+checksum=519a6ebe95b7a325966acfc13fb65c258609940042bf02f086ef2a5f4e59cbb6
conflicts="MoarVM"
do_check() {
next reply other threads:[~2023-09-17 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 13:12 m3tav3rse [this message]
2023-09-18 19:00 ` [PR PATCH] [Merged]: " Duncaen
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-46102@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).