From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core178, updated. 5ca80b3b8f1f5600f0f2c01bd6ff4945fc983244
Date: Mon, 14 Aug 2023 15:54:55 +0000 [thread overview]
Message-ID: <4RPf9W2rwcz2y11@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, core178 has been updated
via 5ca80b3b8f1f5600f0f2c01bd6ff4945fc983244 (commit)
from 41e33931526f9a071acc1f849cbf1d06901a430d (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 5ca80b3b8f1f5600f0f2c01bd6ff4945fc983244
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Aug 8 16:45:12 2023 +0000
Bump PAK_VER for haproxy/keepalived/monit/nmap
This is required as older versions might be linked against older
versions of OpenSSL.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/haproxy | 2 +-
lfs/keepalived | 2 +-
lfs/monit | 2 +-
lfs/nmap | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/lfs/haproxy b/lfs/haproxy
index 6e18995e5..335459fe4 100644
--- a/lfs/haproxy
+++ b/lfs/haproxy
@@ -36,7 +36,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = haproxy
-PAK_VER = 25
+PAK_VER = 26
DEPS =
diff --git a/lfs/keepalived b/lfs/keepalived
index 93d5e9ea0..22bd22dd3 100644
--- a/lfs/keepalived
+++ b/lfs/keepalived
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = keepalived
-PAK_VER = 13
+PAK_VER = 14
DEPS =
diff --git a/lfs/monit b/lfs/monit
index d243be460..4e6782afe 100644
--- a/lfs/monit
+++ b/lfs/monit
@@ -33,7 +33,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = monit
-PAK_VER = 21
+PAK_VER = 22
DEPS =
diff --git a/lfs/nmap b/lfs/nmap
index 52fd077b7..16a3c2e7f 100644
--- a/lfs/nmap
+++ b/lfs/nmap
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = nmap
-PAK_VER = 15
+PAK_VER = 16
DEPS =
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-08-14 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4RPf9W2rwcz2y11@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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