Github messages for voidlinux
 help / color / mirror / Atom feed
From: caughtquick <caughtquick@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hexchat: update to 2.16.2.
Date: Tue, 13 Feb 2024 23:14:34 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48709@inbox.vuxu.org> (raw)

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

There is a new pull request by caughtquick against master on the void-packages repository

https://github.com/caughtquick/void-packages hexchat
https://github.com/void-linux/void-packages/pull/48709

hexchat: update to 2.16.2.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### 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, (x86_64-glibc)



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

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

From e35e4953021cb5515026bf06a200f4b758100ecc Mon Sep 17 00:00:00 2001
From: caughtquick <abhijit@sipahimalani.me>
Date: Tue, 13 Feb 2024 14:13:40 -0800
Subject: [PATCH] hexchat: update to 2.16.2.

---
 srcpkgs/hexchat/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/hexchat/template b/srcpkgs/hexchat/template
index b894acbd74a97..dc07b4ffa949d 100644
--- a/srcpkgs/hexchat/template
+++ b/srcpkgs/hexchat/template
@@ -1,6 +1,6 @@
 # Template file for 'hexchat'
 pkgname=hexchat
-version=2.16.1
+version=2.16.2
 revision=7
 build_style=meson
 configure_args="-Ddbus=enabled -Dtls=enabled
@@ -17,7 +17,7 @@ license="GPL-2.0-or-later"
 homepage="https://hexchat.github.io/"
 changelog="https://hexchat.readthedocs.org/en/latest/changelog.html"
 distfiles="https://github.com/hexchat/hexchat/archive/v${version}.tar.gz"
-checksum=f15bc487312a96a902e042e8f197a8494a29bcf4a00bbfd276a5e8154263bfe5
+checksum=486d73cdb6a89fa91cfbe242107901d06e777bea25956a7786c4a831a2caa0e3
 build_options="LuaJIT"
 lib32disabled=yes
 

             reply	other threads:[~2024-02-13 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 22:14 caughtquick [this message]
2024-02-13 22:18 ` classabbyamp
2024-02-13 23:11 ` caughtquick
2024-02-13 23:15 ` [PR PATCH] [Updated] " caughtquick
2024-02-14  7:22 ` 0x5c
2024-02-14  7:24 ` caughtquick
2024-02-14  7:24 ` caughtquick
2024-02-14  7:25 ` 0x5c
2024-02-14  7:27 ` [PR PATCH] [Closed]: " caughtquick
2024-02-18 12:19 [PR PATCH] " zlice
2024-02-19 22:43 0x5c

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-48709@inbox.vuxu.org \
    --to=caughtquick@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).