Github messages for voidlinux
 help / color / mirror / Atom feed
From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] halloy: update to 2023.5
Date: Mon, 13 Nov 2023 00:06:32 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47187@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1247 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/47187

halloy: update to 2023.5
<!-- 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/47187.patch is attached

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

From 8ce12bb665c8b793f51305154ca731a445633663 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Mon, 13 Nov 2023 00:03:29 +0100
Subject: [PATCH] halloy: update to 2023.5

---
 srcpkgs/halloy/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/halloy/template b/srcpkgs/halloy/template
index 0520619b689a3..f5087da99755d 100644
--- a/srcpkgs/halloy/template
+++ b/srcpkgs/halloy/template
@@ -1,7 +1,7 @@
 # Template file for 'halloy'
 pkgname=halloy
-version=2023.4
-revision=2
+version=2023.5
+revision=1
 build_style=cargo
 hostmakedepends="pkg-config"
 makedepends="libglvnd-devel openssl-devel wayland-devel"
@@ -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=a3440c82b1ec0300f206109d15c53cf23584760f3f7d547e047cf0fe592296f3
+checksum=2d20d4baa6e4502b0455972299dfc42c2365a98d6411637412ca01f2fb7ec5be
 
 post_install() {
 	vinstall assets/linux/org.squidowl.halloy.appdata.xml 644 usr/share/metainfo

             reply	other threads:[~2023-11-12 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 23:06 tranzystorekk [this message]
2023-11-13  5:01 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47187@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).