Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pounce: update to 2.4.
Date: Mon, 12 Jul 2021 22:57:11 +0200	[thread overview]
Message-ID: <20210712205711.CWYVcjxX1V0j7Xyx9f-KK2lrv-S7_kVNNO0B7zfqdfM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31908@inbox.vuxu.org>

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

There is an updated pull request by paper42 against master on the void-packages repository

https://github.com/paper42/void-packages pounce-2.4
https://github.com/void-linux/void-packages/pull/31908

pounce: update to 2.4.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/31908.patch is attached

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

From 54cbdf84da25446bf2fdd98ad03ee3d926ab3483 Mon Sep 17 00:00:00 2001
From: Michal Vasilek <michal@vasilek.cz>
Date: Sun, 11 Jul 2021 15:27:44 +0200
Subject: [PATCH] pounce: update to 2.4.

---
 srcpkgs/pounce/template | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/pounce/template b/srcpkgs/pounce/template
index 4e33113d349b..4e955404312c 100644
--- a/srcpkgs/pounce/template
+++ b/srcpkgs/pounce/template
@@ -1,14 +1,15 @@
 # Template file for 'pounce'
 pkgname=pounce
-version=2.3
-revision=2
+version=2.4
+revision=1
 build_style=gnu-configure
 make_build_target="all"
 hostmakedepends="pkg-config"
-makedepends="libtls-devel"
+makedepends="libtls-devel openssl-devel"
+depends="openssl"
 short_desc="Multi-client, TLS-only IRC bouncer"
-maintainer="Paper <paper@tilde.institute>"
+maintainer="Michal Vasilek <michal@vasilek.cz>"
 license="GPL-3.0-or-later"
 homepage="https://git.causal.agency/pounce/"
 distfiles="https://git.causal.agency/pounce/snapshot/pounce-$version.tar.gz"
-checksum=47e77cf01ccd94c6ecb83410d7f832426de61e28573b7aa4ac60fec5ac3f468b
+checksum=0fe406700a80798eb669db90bef73cc4a644a29a2a36ea7178fed73623050a21

  parent reply	other threads:[~2021-07-12 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11 13:33 [PR PATCH] " paper42
2021-07-12  6:07 ` [PR REVIEW] " ericonr
2021-07-12 20:57 ` paper42 [this message]
2021-07-12 20:57 ` paper42
2021-07-12 20:58 ` paper42
2021-07-13  1:34 ` [PR REVIEW] " ericonr
2021-07-14 14:40 ` [PR PATCH] [Updated] " paper42
2021-07-14 14:40 ` [PR REVIEW] " paper42
2021-07-14 14:44 ` [PR PATCH] [Merged]: " ericonr

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=20210712205711.CWYVcjxX1V0j7Xyx9f-KK2lrv-S7_kVNNO0B7zfqdfM@z \
    --to=paper42@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).