From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 18864e9b4221efccac54fddd274ca77f01385029
Date: Fri, 9 May 2025 12:51:38 +0000 (UTC) [thread overview]
Message-ID: <4Zv85Q4vRpz2xRC@people01.haj.ipfire.org> (raw)
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, next has been updated
via 18864e9b4221efccac54fddd274ca77f01385029 (commit)
from acc61093b1c34b590dadb7cbdd864e04ab589498 (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 18864e9b4221efccac54fddd274ca77f01385029
Author: Matthias Fischer <matthias.fischer@ipfire.org>
Date: Fri May 9 12:33:37 2025 +0200
monit: Update to 5.35.2
For details see:
https://mmonit.com/monit/changes/
"Fixed: An issue where Monit with a short poll cycle could skip
sleep intervals, run checks continuously, and use CPU
excessively when using numerous "check program" tests."
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/monit | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/monit b/lfs/monit
index c8995599b..2b3c69c5c 100644
--- a/lfs/monit
+++ b/lfs/monit
@@ -24,7 +24,7 @@
include Config
-VER = 5.35.1
+VER = 5.35.2
SUMMARY = Utility for monitoring services on a Unix system
THISAPP = monit-$(VER)
@@ -33,7 +33,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = monit
-PAK_VER = 29
+PAK_VER = 30
DEPS =
@@ -47,7 +47,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 6718984afde770dcffb4702fa4590d6615748702e58791e434232cb89818724ac5caac398c83b6a4725b464013a2010e3a31a90829714cd326b88e9fab02b779
+$(DL_FILE)_BLAKE2 = 36ffdf106ac1c800817fd45bd41e444bfbfc483e13a6743ad2b7167e0e5efe612649c90ca7be2a58e6741c6b297c8677e337d9f1b6b451aadbea62eab7ac561a
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-05-09 12:51 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=4Zv85Q4vRpz2xRC@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