From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] batsignal: update to 1.5.0.
Date: Sun, 24 Jul 2022 22:13:34 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38252@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages batsignal-1.5.0
https://github.com/void-linux/void-packages/pull/38252
batsignal: update to 1.5.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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{glibc,musl}
A patch file from https://github.com/void-linux/void-packages/pull/38252.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-batsignal-1.5.0-38252.patch --]
[-- Type: text/x-diff, Size: 1055 bytes --]
From 3d31b24770600a8164db31bfa407c3bb4559f6a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sun, 24 Jul 2022 21:03:08 +0100
Subject: [PATCH] batsignal: update to 1.5.0.
---
srcpkgs/batsignal/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/batsignal/template b/srcpkgs/batsignal/template
index a8d55e6ad30f..a6f112d6da1d 100644
--- a/srcpkgs/batsignal/template
+++ b/srcpkgs/batsignal/template
@@ -1,6 +1,6 @@
# Template file for 'batsignal'
pkgname=batsignal
-version=1.3.2
+version=1.5.0
revision=1
build_style=gnu-makefile
make_use_env=yes
@@ -11,7 +11,7 @@ maintainer="André Cerqueira <acerqueira021@gmail.com>"
license="ISC"
homepage="https://github.com/electrickite/batsignal"
distfiles="https://github.com/electrickite/batsignal/archive/${version}.tar.gz"
-checksum=d8ecb26435b4a49f804ebc2bc1f18215a4c7cfd2a5de7e2a1ccef5263e1c04e7
+checksum=be3196bac5f369348123d78cacc3d20d29005a8bc93bcbc4541231843a5a7f5f
post_install() {
vlicense LICENSE
next reply other threads:[~2022-07-24 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 20:13 motorto [this message]
2022-07-24 21:29 ` [PR PATCH] [Updated] " motorto
2022-07-25 8:15 ` motorto
2022-07-25 11:23 ` [PR REVIEW] " sgn
2022-07-25 11:23 ` sgn
2022-07-25 11:24 ` sgn
2022-07-25 11:33 ` [PR PATCH] [Updated] " motorto
2022-07-25 11:35 ` motorto
2022-07-25 12:04 ` [PR PATCH] [Updated] " sgn
2022-07-25 12:05 ` sgn
2022-07-25 12:08 ` sgn
2022-07-25 12:13 ` [PR PATCH] [Updated] " sgn
2022-07-25 12:36 ` motorto
2022-07-25 12:38 ` motorto
2022-07-25 12:43 ` motorto
2022-07-25 14:26 ` [PR PATCH] [Merged]: " sgn
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-38252@inbox.vuxu.org \
--to=motorto@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).