From: ArmedAviator <ArmedAviator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] haproxy: update to 2.2.4
Date: Thu, 15 Oct 2020 04:43:10 +0200 [thread overview]
Message-ID: <20201015024310.x4LCrwCog0YVeGTJVVXSg-XFS-npIi7daBrVTHAN6yE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25005@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
There is an updated pull request by ArmedAviator against master on the void-packages repository
https://github.com/ArmedAviator/void-packages haproxy
https://github.com/void-linux/void-packages/pull/25005
haproxy: update to 2.2.4
Tested working. This brings HAProxy to the latest LTS branch.
A patch file from https://github.com/void-linux/void-packages/pull/25005.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-haproxy-25005.patch --]
[-- Type: text/x-diff, Size: 1345 bytes --]
From 210a320de54d4547eb391273722d1b4ab6a3966a Mon Sep 17 00:00:00 2001
From: Rich G <rich@richgannon.net>
Date: Sun, 20 Sep 2020 23:11:48 -0400
Subject: [PATCH] haproxy: update to 2.2.4
---
srcpkgs/haproxy/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/haproxy/template b/srcpkgs/haproxy/template
index a51a4126e14..237e4ff006e 100644
--- a/srcpkgs/haproxy/template
+++ b/srcpkgs/haproxy/template
@@ -1,17 +1,17 @@
# Template file for 'haproxy'
pkgname=haproxy
-version=2.1.7
-revision=3
+version=2.2.4
+revision=1
build_style=gnu-makefile
make_install_args="SBINDIR=${DESTDIR}/usr/bin DOCDIR=${DESTDIR}/usr/share/doc/${pkgname}"
makedepends="libatomic-devel libressl-devel lua53-devel pcre-devel"
checkdepends="varnish"
short_desc="Reliable, high performance TCP/HTTP load balancer"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Rich Gannon <rich@richgannon.net>"
license="GPL-2.0-or-later, LGPL-2.1-or-later"
homepage="https://www.haproxy.org"
distfiles="${homepage}/download/${version%.*}/src/${pkgname}-${version}.tar.gz"
-checksum=392e6cf18e75fe7e166102e8c4512942890a0b5ae738f6064faab4687f60a339
+checksum=87a4d9d4ff8dc3094cb61bbed4a8eed2c40b5ac47b9604daebaf036d7b541be2
haproxy_homedir="/var/lib/${pkgname}"
make_dirs="$haproxy_homedir 0750 ${pkgname} ${pkgname}"
next prev parent reply other threads:[~2020-10-15 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 3:15 [PR PATCH] haproxy: update to 2.2.3 ArmedAviator
2020-10-15 2:41 ` [PR PATCH] [Updated] " ArmedAviator
2020-10-15 2:43 ` ArmedAviator [this message]
2020-11-01 22:30 ` [PR PATCH] [Updated] haproxy: update to 2.2.4 ArmedAviator
2020-12-30 7:10 ` the-maldridge
2020-12-30 7:10 ` [PR PATCH] [Closed]: " the-maldridge
2020-10-28 18:41 [PR PATCH] " zdykstra
2020-10-30 17:13 ` [PR PATCH] [Updated] " zdykstra
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=20201015024310.x4LCrwCog0YVeGTJVVXSg-XFS-npIi7daBrVTHAN6yE@z \
--to=armedaviator@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).