Github messages for voidlinux
 help / color / mirror / Atom feed
From: uhlin <uhlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] swirc: update to 3.4.0.
Date: Sat, 11 Feb 2023 16:21:19 +0100	[thread overview]
Message-ID: <20230211152119.fNVBAaqkrz5fbTr-Lbfi-O7bm6fRhRX4_6b7Z7frzL0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42179@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

There is an updated 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/42179

swirc: update to 3.4.0.
Swirc 3.4.0 out

#### 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:
  - armv6l-musl **cross**


A patch file from https://github.com/void-linux/void-packages/pull/42179.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-42179.patch --]
[-- Type: text/x-diff, Size: 1706 bytes --]

From 260b7f461b77a6801163ec69975b5e81eec7378f Mon Sep 17 00:00:00 2001
From: Markus Uhlin <markus.uhlin@bredband.net>
Date: Fri, 10 Feb 2023 10:40:39 +0100
Subject: [PATCH] swirc: update to 3.4.0.

---
 srcpkgs/swirc/template | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/swirc/template b/srcpkgs/swirc/template
index 9afe569e7a02..af6800980cd6 100644
--- a/srcpkgs/swirc/template
+++ b/srcpkgs/swirc/template
@@ -1,6 +1,6 @@
 # Template file for 'swirc'
 pkgname=swirc
-version=3.3.9
+version=3.4.0
 revision=1
 build_style=configure
 configure_args="$(vopt_with notify libnotify)"
@@ -8,16 +8,16 @@ make_build_args="PREFIX=/usr"
 make_check_args="PREFIX=/usr"
 make_install_args="PREFIX=/usr"
 hostmakedepends="gettext-devel-tools pkg-config which"
-makedepends="gettext-devel libcurl-devel libidn-devel ncurses-devel openssl-devel
- $(vopt_if notify libnotify-devel)"
+makedepends="gettext-devel hunspell-devel libcurl-devel libidn-devel
+ ncurses-devel openssl-devel $(vopt_if notify libnotify-devel)"
 checkdepends="cmocka-devel"
 short_desc="Curses ICB and IRC client"
 maintainer="Markus Uhlin <markus.uhlin@bredband.net>"
 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/${pkgname}-${version}.tgz"
-checksum=4326dcf521d2a0ca3c55ed289fea0c0d1a289dcc158c80f4aee207ff2085ab37
+distfiles="https://www.nifty-networks.net/swirc/releases/swirc-${version}.tgz"
+checksum=3142273db2568a9dd812abf87112edb01fdcac6b4ee7e61ebb5fc96f60a95a18
 
 build_options="notify"
 build_options_default="notify"

  parent reply	other threads:[~2023-02-11 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 10:00 [PR PATCH] " uhlin
2023-02-11  4:10 ` [PR REVIEW] " classabbyamp
2023-02-11 14:24 ` uhlin
2023-02-11 15:00 ` classabbyamp
2023-02-11 15:21 ` uhlin [this message]
2023-02-11 15:25 ` uhlin
2023-02-11 15:40 ` [PR PATCH] [Merged]: " classabbyamp

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=20230211152119.fNVBAaqkrz5fbTr-Lbfi-O7bm6fRhRX4_6b7Z7frzL0@z \
    --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).