From: uhlin <uhlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] swirc: update to 3.4.3.
Date: Fri, 10 Mar 2023 19:02:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42692@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
There is a new pull request by uhlin against master on the void-packages repository
https://github.com/uhlin/void-packages master
https://github.com/void-linux/void-packages/pull/42692
swirc: update to 3.4.3.
Today I released Swirc 3.4.3 which comes with code improvements and new translations.
No new bugs were fixed/found.
#### 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 (if supported. mark crossbuilds):
- armv6l-musl **cross**
A patch file from https://github.com/void-linux/void-packages/pull/42692.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-42692.patch --]
[-- Type: text/x-diff, Size: 1084 bytes --]
From 63685e3e2b356e731445d941669b41fa9b1c263b Mon Sep 17 00:00:00 2001
From: Markus Uhlin <markus.uhlin@bredband.net>
Date: Fri, 10 Mar 2023 18:53:45 +0100
Subject: [PATCH] swirc: update to 3.4.3.
---
srcpkgs/swirc/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/swirc/template b/srcpkgs/swirc/template
index 624e294f3300..24fdea295b38 100644
--- a/srcpkgs/swirc/template
+++ b/srcpkgs/swirc/template
@@ -1,6 +1,6 @@
# Template file for 'swirc'
pkgname=swirc
-version=3.4.2
+version=3.4.3
revision=1
build_style=configure
configure_args="$(vopt_with notify libnotify)"
@@ -17,7 +17,7 @@ license="BSD-3-Clause, ISC, MIT"
homepage="https://www.nifty-networks.net/swirc"
changelog="https://raw.githubusercontent.com/uhlin/swirc/master/CHANGELOG.md"
distfiles="https://www.nifty-networks.net/swirc/releases/swirc-${version}.tgz"
-checksum=cdfe4d7d5879b40791f759fe94a95dc6b310c54a1c685790fc8d2447ba2fdc97
+checksum=008caf24eedeeeaad85c0f48ee74178545c1467eb55aac5b902fda38d78179c2
build_options="notify"
build_options_default="notify"
next reply other threads:[~2023-03-10 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 18:02 uhlin [this message]
2023-03-10 19:50 ` [PR PATCH] [Merged]: " paper42
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-42692@inbox.vuxu.org \
--to=uhlin@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).