From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pgbouncer: update to 1.17.0.
Date: Wed, 20 Jul 2022 18:10:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38154@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
There is a new pull request by natrys against master on the void-packages repository
https://github.com/natrys/void-packages pgbouncer-1.17.0
https://github.com/void-linux/void-packages/pull/38154
pgbouncer: update to 1.17.0.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/38154.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pgbouncer-1.17.0-38154.patch --]
[-- Type: text/x-diff, Size: 1439 bytes --]
From 24f71e3328c6b3c49c4273b8ba01a11946bae364 Mon Sep 17 00:00:00 2001
From: Imran Khan <imrankhan@teknik.io>
Date: Wed, 20 Jul 2022 22:08:01 +0600
Subject: [PATCH] pgbouncer: update to 1.17.0.
---
srcpkgs/pgbouncer/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/pgbouncer/template b/srcpkgs/pgbouncer/template
index 650e3340f07c..fb60ee74f89e 100644
--- a/srcpkgs/pgbouncer/template
+++ b/srcpkgs/pgbouncer/template
@@ -1,22 +1,22 @@
# Template file for 'pgbouncer'
pkgname=pgbouncer
-version=1.16.1
+version=1.17.0
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config"
makedepends="libevent-devel"
-checkdepends="which postgresql13 postgresql13-client"
+checkdepends="which postgresql14 postgresql14-client"
short_desc="Lightweight connection pooler for PostgreSQL"
maintainer="Kyle Nusbaum <knusbaum+void@sdf.org>"
license="ISC"
homepage="https://pgbouncer.github.io/"
changelog="https://raw.githubusercontent.com/pgbouncer/pgbouncer/master/NEWS.md"
distfiles="https://pgbouncer.github.io/downloads/files/${version}/pgbouncer-${version}.tar.gz"
-checksum=087477e9e4766d032b04b7b006c0c8d64160a54141a7bfc2c6e5ae7ae11bf7fc
+checksum=657309b7bc5c7a85cbf70a9a441b535f7824123081eabb7ba86d00349a256e23
make_check=ci-skip # Postgres server can't be run as root
pre_check() {
- . /etc/profile.d/postgresql13.sh
+ . /etc/profile.d/postgresql14.sh
}
post_install() {
next reply other threads:[~2022-07-20 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 16:10 natrys [this message]
2022-07-20 16:58 ` [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-38154@inbox.vuxu.org \
--to=natrys@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).