From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] haproxy: Update to 2.4.15
Date: Tue, 05 Apr 2022 13:39:56 +0200 [thread overview]
Message-ID: <981071dc-80a6-5871-8418-1513098dc2ee@ipfire.org> (raw)
In-Reply-To: <6ee9ad17-9b6b-f81d-2bc2-1760e36aea9b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 04/04/2022 07:31, Peter Müller wrote:
> The changelog of the entire 2.4.x series can be retrieved from
> https://www.haproxy.org/download/2.4/src/CHANGELOG .
>
> As-promised-to: Michael Tremer <michael.tremer(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> lfs/haproxy | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/lfs/haproxy b/lfs/haproxy
> index 59e17e03a..96911574d 100644
> --- a/lfs/haproxy
> +++ b/lfs/haproxy
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -26,7 +26,9 @@ include Config
>
> SUMMARY = The Reliable, High Performance TCP/HTTP Load Balancer
>
> -VER = 2.2.4
> +VER = 2.4.15
> +
> +# From: https://www.haproxy.org/download/2.4/src/haproxy-2.4.15.tar.gz
>
> THISAPP = haproxy-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -34,7 +36,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = haproxy
> -PAK_VER = 19
> +PAK_VER = 20
>
> DEPS =
>
> @@ -52,7 +54,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = c53da911f09a5b35ae97709691754aceed09b01dffa27ee69368d26f552c1b87d149477ad8ab0410564e5ef1d520c91e069b36a9f3a5588a8cf9feb3139f9181
> +$(DL_FILE)_BLAKE2 = 425444a54e22cca8d15cb808283be3baefcd2ce56447d91bce3b4f4b7f6606e03d2eb8a242891c619cfd0fad9aba5bb84026c68d41f07cd55f083481df234899
>
> install : $(TARGET)
>
prev parent reply other threads:[~2022-04-05 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 5:31 Peter Müller
2022-04-05 11:39 ` Adolf Belka [this message]
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=981071dc-80a6-5871-8418-1513098dc2ee@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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