From: famfo <famfo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Update libstrophe and profanity
Date: Tue, 10 Oct 2023 15:05:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46556@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
There is a new pull request by famfo against master on the void-packages repository
https://github.com/famfo/void-packages update-packages
https://github.com/void-linux/void-packages/pull/46556
Update libstrophe and profanity
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/46556.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-packages-46556.patch --]
[-- Type: text/x-diff, Size: 2330 bytes --]
From ca77978872aa78c7e4cfe770002950cb42b14641 Mon Sep 17 00:00:00 2001
From: famfo <famfo@famfo.xyz>
Date: Tue, 10 Oct 2023 15:02:47 +0200
Subject: [PATCH] Update libstrophe and profanity
---
srcpkgs/libstrophe/template | 6 +++---
srcpkgs/profanity/template | 8 ++++----
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/libstrophe/template b/srcpkgs/libstrophe/template
index 617d333766ef9..5780d39e3fe76 100644
--- a/srcpkgs/libstrophe/template
+++ b/srcpkgs/libstrophe/template
@@ -1,7 +1,7 @@
# Template file for 'libstrophe'
pkgname=libstrophe
-version=0.12.2
-revision=2
+version=0.12.3
+revision=3
build_style=gnu-configure
configure_args="$(vopt_enable cares) $(vopt_enable tls)"
hostmakedepends="automake libtool pkg-config"
@@ -13,7 +13,7 @@ license="GPL-3.0-only"
homepage="http://strophe.im/libstrophe/"
changelog="https://raw.githubusercontent.com/strophe/libstrophe/master/ChangeLog"
distfiles="https://github.com/strophe/libstrophe/archive/${version}.tar.gz"
-checksum=049232e3968ad65c65e08601cb3de171d3a25d154b6f14332c35a7bf961e2c9d
+checksum=e93a77b78f228201ee0278dbdd29142a943263df7e62278e25eacfe814e0bb34
build_options="cares tls"
build_options_default="tls"
diff --git a/srcpkgs/profanity/template b/srcpkgs/profanity/template
index 9cd9d077d9479..c380d24a40f5d 100644
--- a/srcpkgs/profanity/template
+++ b/srcpkgs/profanity/template
@@ -1,7 +1,7 @@
# Template file for 'profanity'
pkgname=profanity
-version=0.13.1
-revision=2
+version=0.14.0
+revision=1
build_style=gnu-configure
configure_args="$(vopt_enable notify notifications) $(vopt_enable otr)
$(vopt_enable pgp) $(vopt_enable python python-plugins) $(vopt_enable plugins)
@@ -19,8 +19,8 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-3.0-or-later"
homepage="https://profanity-im.github.io/"
changelog="https://raw.githubusercontent.com/profanity-im/profanity/master/CHANGELOG"
-distfiles="https://github.com/boothj5/profanity/releases/download/${version}/profanity-${version}.tar.gz"
-checksum=2b5075272e7ec9d9c991542e592b1d474fff88c61c66e7e23096ad306ed2c84a
+distfiles="https://github.com/profanity-im/profanity/releases/download/${version}/profanity-${version}.tar.gz"
+checksum=fd23ffd38a31907974a680a3900c959e14d44e16f1fb7df2bdb7f6c67bd7cf7f
case "$XBPS_TARGET_MACHINE" in
arm*)
next reply other threads:[~2023-10-10 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 13:05 famfo [this message]
2023-10-10 18:27 ` [PR PATCH] [Updated] libstrophe: update to 0.12.3 profanity: update to 0.14.0 famfo
2023-10-10 23:34 ` famfo
2023-10-13 10:02 ` lm41
2024-01-06 18:43 ` yoshiyoshyosh
2024-01-07 13:14 ` [PR PATCH] [Closed]: " famfo
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-46556@inbox.vuxu.org \
--to=famfo@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).