public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] zabbix_agentd: Update to 6.0.22 (LTS)
Date: Mon, 30 Oct 2023 10:04:29 +0000	[thread overview]
Message-ID: <FD008005-FEFC-4481-AE09-03AD8FF93F68@ipfire.org> (raw)
In-Reply-To: <36cf6aacd372b9be2c52e5b1021651a9d79c82af.camel@sicho.home>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

Thank you. Merged!

> On 27 Oct 2023, at 20:44, Robin Roevens <robin.roevens(a)disroot.org> wrote:
> 
> For reference, the download link for the zabbix_agentd source used in
> this patch:
> https://cdn.zabbix.com/zabbix/sources/stable/6.0/zabbix-6.0.22.tar.gz
> 
> Regards
> 
> Robin
> 
> Robin Roevens schreef op vr 27-10-2023 om 21:40 [+0200]:
>> - Update from version 6.0.21 to 6.0.22
>> - Update of rootfile not required
>> 
>> Bugs fixed:
>> - ZBX-23417: Fixed possible memory leak when checking modbus.get[]
>> item
>> New Features and Improvements:
>> - ZBXNEXT-6554: Increased remote command execution limits to 16MB
>> 
>> Full changelogs since 6.0.21:
>> - https://www.zabbix.com/rn/rn6.0.22
>> ---
>>  lfs/zabbix_agentd | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>> 
>> diff --git a/lfs/zabbix_agentd b/lfs/zabbix_agentd
>> index 7c0d01150..0033d9a2c 100644
>> --- a/lfs/zabbix_agentd
>> +++ b/lfs/zabbix_agentd
>> @@ -26,7 +26,7 @@ include Config
>>  
>>  SUMMARY    = Zabbix Agent
>>  
>> -VER        = 6.0.21
>> +VER        = 6.0.22
>>  
>>  THISAPP    = zabbix-$(VER)
>>  DL_FILE    = $(THISAPP).tar.gz
>> @@ -34,7 +34,7 @@ DL_FROM    = $(URL_IPFIRE)
>>  DIR_APP    = $(DIR_SRC)/$(THISAPP)
>>  TARGET     = $(DIR_INFO)/$(THISAPP)
>>  PROG       = zabbix_agentd
>> -PAK_VER    = 10
>> +PAK_VER    = 11
>>  
>>  DEPS       = fping
>>  
>> @@ -48,7 +48,7 @@ objects = $(DL_FILE)
>>  
>>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>  
>> -$(DL_FILE)_BLAKE2 =
>> 0928695a5f2729765a5b1fa31df410d585b50ef40a9d8379d6243c256c88234ac916b
>> faf13f62a8e28bb8fb4be48e83c1aecfd01f66dc45d4e25a20761d8ef82
>> +$(DL_FILE)_BLAKE2 =
>> bba7911a24b00827c58d84938b5786d07f1eb44cbcad94cddf68b484ac9a2f514beb6
>> 0225d006b8cefc5bbf92e51da27f26d9f6681e10f6322ed0841394e8d9d
>>  
>>  install : $(TARGET)
>>  
>> -- 
>> 2.41.0
>> 
>> 
> 
> -- 
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
> 


  reply	other threads:[~2023-10-30 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 19:40 Robin Roevens
2023-10-27 19:44 ` Robin Roevens
2023-10-30 10:04   ` Michael Tremer [this message]
2023-10-27 19:49 ` [PATCH 2/2] zabbix_agentd: Fix ipfire.net.gateway.ping Robin Roevens

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=FD008005-FEFC-4481-AE09-03AD8FF93F68@ipfire.org \
    --to=michael.tremer@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