public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: "IPFire: Development" <development@lists.ipfire.org>
Subject: [PATCH] NRPE: Update to 4.2.0
Date: Thu, 29 Oct 2026 14:38:00 +0000	[thread overview]
Message-ID: <5b5c66c6-340b-4445-999c-8a782a5ad8de@ipfire.org> (raw)

Changelog according to https://github.com/NagiosEnterprises/nrpe/blob/master/CHANGELOG.md:

ENHANCEMENTS

    Added testing and code coverage reporting (Doug Nazar)
    Added config option to toggle between IPv4/IPv6 (Doug Nazar)
    Added config option to enable or disable SSL/TLS (Doug Nazar)

FIXES

    Fixed compilation without OpenSSL engine.h (Emmett Kapsner)
    Fixed various warnings when building with -Wall (Doug Nazar)
    Fixed compilation on AIX and Solaris (Doug Nazar)
    Fixed various memory leaks (Doug Nazar)
    Fixed debug display of ACL IP addresses (Doug Nazar)
    Fixed my_system() buffer error (Doug Nazar)
    Fixed an issue where Makefile would always make all (Doug Nazar)
    Fixed an issue where utils.c would be compiled twice (Doug Nazar)

https://exchange.nagios.org/directory/addons/monitoring-agents/nrpe-2d-nagios-remote-plugin-executor/details/
does not list this update yet, despite being released more than a week
ago. The GitHub download returns an archive carrying a redundant "nrpe-"
file prefix, hence requiring $DL_FILE and $DIR_APP adjustments.

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
---
 lfs/nagios_nrpe | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/lfs/nagios_nrpe b/lfs/nagios_nrpe
index 5547f1d75..50bc4cfb7 100644
--- a/lfs/nagios_nrpe
+++ b/lfs/nagios_nrpe
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2025  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2026  IPFire Team  <info@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,15 +26,15 @@ include Config
 
 SUMMARY    = Nagios Remote Plug-In Executor
 
-VER        = 4.1.3
+VER        = 4.2.0
 
 THISAPP    = nrpe-$(VER)
-DL_FILE    = $(THISAPP).tar.gz
+DL_FILE    = nrpe-$(THISAPP).tar.gz
 DL_FROM    = $(URL_IPFIRE)
-DIR_APP    = $(DIR_SRC)/$(THISAPP)
+DIR_APP    = $(DIR_SRC)/nrpe-$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = nagios_nrpe
-PAK_VER    = 14
+PAK_VER    = 15
 
 DEPS       = nagios-plugins
 
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 9337bfd0226ddb72cbc94aca7e30a94a1b325874d5bf631ff84786f65214628d90d6adec0de13d425b71a14b5ac36bf75c3561ef17b27773c8cb88ef2316be66
+$(DL_FILE)_BLAKE2 = b4cef10b3b95204ef3c6f829f2791749f2312d70c711eafcbb01266a5b57da3f47ca296278d02d0266708a4a0671c4992e371554dc382935d13f784114cd7634
 
 install : $(TARGET)
 
-- 
2.51.0


                 reply	other threads:[~2026-10-29 14:38 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=5b5c66c6-340b-4445-999c-8a782a5ad8de@ipfire.org \
    --to=peter.mueller@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