From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] halloy: update to 2024.14
Date: Tue, 29 Oct 2024 12:20:34 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52834@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
There is a new pull request by tranzystorekk against master on the void-packages repository
https://github.com/tranzystorekk/void-packages halloy
https://github.com/void-linux/void-packages/pull/52834
halloy: update to 2024.14
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/52834.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-halloy-52834.patch --]
[-- Type: text/x-diff, Size: 1124 bytes --]
From 34da6656e34b4412acbc60e50365f4780c486b4e Mon Sep 17 00:00:00 2001
From: tranzystorekk <tranzystorek.io@protonmail.com>
Date: Tue, 29 Oct 2024 11:40:42 +0100
Subject: [PATCH] halloy: update to 2024.14
---
srcpkgs/halloy/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/halloy/template b/srcpkgs/halloy/template
index 28612ba559c671..3e09bf62fdd6fb 100644
--- a/srcpkgs/halloy/template
+++ b/srcpkgs/halloy/template
@@ -1,6 +1,6 @@
# Template file for 'halloy'
pkgname=halloy
-version=2024.12
+version=2024.14
revision=1
build_style=cargo
hostmakedepends="pkg-config"
@@ -11,7 +11,7 @@ license="GPL-3.0-or-later"
homepage="https://github.com/squidowl/halloy"
changelog="https://raw.githubusercontent.com/squidowl/halloy/main/CHANGELOG.md"
distfiles="https://github.com/squidowl/halloy/archive/refs/tags/${version}.tar.gz"
-checksum=df773c2e7ad6bf335fe2cdfd721f8873550cfb5554a9c1734bae76cee1282871
+checksum=f5f9509770c628e021a9ea8d5eed4b51aa3c7b4a792ff2de55cc1596f6f5c50b
post_install() {
vinstall assets/linux/org.squidowl.halloy.appdata.xml 644 usr/share/metainfo
next reply other threads:[~2024-10-29 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 11:20 tranzystorekk [this message]
2024-10-29 11:36 ` [PR PATCH] [Merged]: " tranzystorekk
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-52834@inbox.vuxu.org \
--to=tranzystorekk@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).