From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Zabbix addon Date: Thu, 30 Mar 2023 14:43:39 +0200 Message-ID: <86293b77-176e-48d2-de66-01f156a202b0@ipfire.org> In-Reply-To: <139ee284e4753449b0ee8b93da93dd77758d6973.camel@sicho.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2004936411527005531==" List-Id: --===============2004936411527005531== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Robin, On 30/03/2023 09:59, Robin Roevens wrote: > Hi Adolf >=20 > I know. I'm keeping watch on the upstream updates. Good to know. > "The problem" is that the agent code is released in one source tree with ag= ent2, server, frontend, windows agent, etc.. and they all share the same vers= ion on each release but that doesn't necessary mean there are actual changes = on the agent code itself. So I'm keeping track of the changelogs for any chan= ges on the Linux agent itself, but since 6.0.6 there weren't any=C2=A0substan= tial changes, if any, on the code of the Linux agent. > So I can provide those update patches, but it would actually just be cosmet= ic :-). I agree that would not make sense to do. I will leave it in your capable hands then to recognise when an update is req= uired. Regards, Adolf. >=20 > Regards > Robin >=20 >=20 > Adolf Belka schreef op di 28-03-2023 om 09:56 [+0200]: >> Hi Robin, >> >> I have noticed that the zabbix_agentd addon is at 6.0.6 (LTS) but the LTS = branch is now at 6.0.14 >> >> Could you look at doing an update patch for it. >> >> >> Regards, >> >> Adolf. >> >> >=20 > --=20 > Dit bericht is gescanned op virussen en andere gevaarlijke > inhoud door *MailScanner* en lijkt schoon te= zijn. --===============2004936411527005531==--