AU: 3 updated - zabbix-agent zabbix-agent.install zabbix-agent2

[skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/2a7a2928b735caf8441c1f679959255cdf33af77
mkevenaar · Mar 26, 2024 · 16451b4 · 16451b4
1 parent 6d7991c
commit 16451b4
Show file tree

Hide file tree

Showing 12 changed files with 31 additions and 31 deletions.
diff --git a/automatic/zabbix-agent.install/legal/VERIFICATION.txt b/automatic/zabbix-agent.install/legal/VERIFICATION.txt
@@ -7,20 +7,20 @@ Package can be verified like this:
 
 1. Go to
 
-   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-amd64-openssl.msi
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-i386-openssl.msi
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-amd64-openssl.msi
 
    to download the installer.
 
 2. You can use one of the following methods to obtain the SHA256 checksum:
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'
 
-   checksum32: 610AB776329F868276E1DD2ACB476AF4147DAB66EBF8C9E2CDEF8C7EDE0F9A9F
-   checksum64: 465552A2D8DE58142A7CA25DE25FE09754EC205A5B10BDB62C09D2AFC66EF34F
+   checksum32: 37F95269541FF6850A14413B7D0CDA101F3B73D42FDFAD3B294DA7E518DE36B1
+   checksum64: 7C1B20D13EEAA9721008DB49083B641A8E834C30AA85E95CB133035108D315F5
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-amd64-openssl.msi
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-i386-openssl.msi
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-amd64-openssl.msi
 
diff --git a/automatic/zabbix-agent.install/tools/chocolateyInstall.ps1 b/automatic/zabbix-agent.install/tools/chocolateyInstall.ps1
@@ -35,8 +35,8 @@ if ($pp.ALLOWDENYKEY) { $SilentArgs += " ALLOWDENYKEY=`"$($pp.ALLOWDENYKEY)`"" }
 $PackageArgs = @{
   PackageName    = $env:ChocolateyPackageName
   FileType       = 'MSI'
-  file          = "$toolsDir\zabbix_agent-6.4.12-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent-6.4.12-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent-5.0.42-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent-5.0.42-windows-amd64-openssl.msi"
   softwareName  = "Zabbix Agent *"
 
   SilentArgs     = $SilentArgs

diff --git a/automatic/zabbix-agent.install/zabbix-agent.install.json b/automatic/zabbix-agent.install/zabbix-agent.install.json
@@ -1,7 +1,7 @@
 {
     "6.2":  "6.2.9",
     "6.0":  "6.0.27",
-    "5.0":  "5.0.41",
+    "5.0":  "5.0.42",
     "4.0":  "4.0.50",
     "4.2":  "4.2.8",
     "5.4":  "5.4.9",

diff --git a/automatic/zabbix-agent.install/zabbix-agent.install.nuspec b/automatic/zabbix-agent.install/zabbix-agent.install.nuspec
@@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>6.4.12</version>
+    <version>5.0.42</version>
     <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
     <owners>Maurice Kevenaar</owners>
     <!-- ============================== -->

diff --git a/automatic/zabbix-agent/legal/VERIFICATION.txt b/automatic/zabbix-agent/legal/VERIFICATION.txt
@@ -7,20 +7,20 @@ Package can be verified like this:
 
 1. Go to
 
-   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-i386-openssl.zip
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-amd64-openssl.zip
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-i386-openssl.zip
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-amd64-openssl.zip
 
    to download the installer.
 
 2. You can use one of the following methods to obtain the SHA256 checksum:
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'
 
-   checksum32: AD05CF01F46CF8660C510244BD15552B8B394B29B4A58C43DCA5CCA1D0C962A4
-   checksum64: D687CD3C28280D265891381E04C14B39F1DB7CC68D13CEA9670F0DA755B9039C
+   checksum32: 83F033109B45F8F4CE3967DB0FE731C55BC564724866ECB8F7DBC70D170A7112
+   checksum64: BBC8E7CDF1C327D6C8E9DAC444B3D87106F20F0C75CD8E316B2B09C240D7B7AE
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-i386-openssl.zip
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent-6.4.12-windows-amd64-openssl.zip
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-i386-openssl.zip
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent-5.0.42-windows-amd64-openssl.zip
 
diff --git a/automatic/zabbix-agent/tools/chocolateyInstall.ps1 b/automatic/zabbix-agent/tools/chocolateyInstall.ps1
@@ -1,5 +1,5 @@
 $ErrorActionPreference = 'Stop';
-$version = '6.4.12'
+$version = '5.0.42'
 $title = 'Zabbix Agent'
 
 $configDir = Join-Path $env:PROGRAMDATA 'zabbix'
@@ -19,8 +19,8 @@ $service = Get-WmiObject -Class Win32_Service -Filter "Name=`'$title`'"
 $PackageArgs = @{
   PackageName    = $env:ChocolateyPackageName
   unzipLocation = $tempDir
-  file          = "$toolsDir\zabbix_agent-6.4.12-windows-i386-openssl.zip"
-  file64        = "$toolsDir\zabbix_agent-6.4.12-windows-amd64-openssl.zip"
+  file          = "$toolsDir\zabbix_agent-5.0.42-windows-i386-openssl.zip"
+  file64        = "$toolsDir\zabbix_agent-5.0.42-windows-amd64-openssl.zip"
 }
 
 try {

diff --git a/automatic/zabbix-agent/zabbix-agent.json b/automatic/zabbix-agent/zabbix-agent.json
@@ -1,7 +1,7 @@
 {
     "6.2":  "6.2.9",
     "6.0":  "6.0.27",
-    "5.0":  "5.0.41",
+    "5.0":  "5.0.42",
     "4.0":  "4.0.50",
     "4.4":  "4.4.9",
     "5.4":  "5.4.12",

diff --git a/automatic/zabbix-agent/zabbix-agent.nuspec b/automatic/zabbix-agent/zabbix-agent.nuspec
@@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>6.4.12</version>
+    <version>5.0.42</version>
     <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
     <owners>Maurice Kevenaar</owners>
     <!-- ============================== -->

diff --git a/automatic/zabbix-agent2/legal/VERIFICATION.txt b/automatic/zabbix-agent2/legal/VERIFICATION.txt
@@ -7,20 +7,20 @@ Package can be verified like this:
 
 1. Go to
 
-   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent2-6.4.12-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent2-6.4.12-windows-amd64-openssl.msi
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent2-5.0.42-windows-i386-openssl.msi
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent2-5.0.42-windows-amd64-openssl.msi
 
    to download the installer.
 
 2. You can use one of the following methods to obtain the SHA256 checksum:
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'
 
-   checksum32: 5AAB19C439B4281A4CECB2C88758EC8120A143EB668416E010088BBDD3A6A2CD
-   checksum64: 8E957A0DD7FD6BA102C54816A83C596BE7BBBE757F8983711FFF702FACB0BAC4
+   checksum32: 77ACFD513176CC25E0096A62826B0E24B8377FD6F2660AD26E217858E62FD63F
+   checksum64: 6703ACC40C2031A1CF99A0079831A3B97F0468AA1DA106EC6B7F318FD9025D05
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent2-6.4.12-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.12/zabbix_agent2-6.4.12-windows-amd64-openssl.msi
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent2-5.0.42-windows-i386-openssl.msi
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.42/zabbix_agent2-5.0.42-windows-amd64-openssl.msi
 
diff --git a/automatic/zabbix-agent2/tools/chocolateyinstall.ps1 b/automatic/zabbix-agent2/tools/chocolateyinstall.ps1
@@ -39,8 +39,8 @@ if ($pp.ALLOWDENYKEY) { $SilentArgs += " ALLOWDENYKEY=`"$($pp.ALLOWDENYKEY)`"" }
 $PackageArgs = @{
   PackageName    = $env:ChocolateyPackageName
   FileType       = 'MSI'
-  file          = "$toolsDir\zabbix_agent2-6.4.12-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent2-6.4.12-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent2-5.0.42-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent2-5.0.42-windows-amd64-openssl.msi"
   softwareName  = "Zabbix Agent *"
 
   SilentArgs     = $SilentArgs

diff --git a/automatic/zabbix-agent2/zabbix-agent2.json b/automatic/zabbix-agent2/zabbix-agent2.json
@@ -1,7 +1,7 @@
 {
     "6.2":  "6.2.9",
     "6.0":  "6.0.27",
-    "5.0":  "5.0.41",
+    "5.0":  "5.0.42",
     "5.2":  "5.2.7",
     "5.4":  "5.4.12",
     "6.4":  "6.4.12"

diff --git a/automatic/zabbix-agent2/zabbix-agent2.nuspec b/automatic/zabbix-agent2/zabbix-agent2.nuspec
@@ -26,7 +26,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <!-- version should MATCH as closely as possible with the underlying software -->
     <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
     <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
-    <version>6.4.12</version>
+    <version>5.0.42</version>
     <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
     <owners>Maurice Kevenaar</owners>
     <!-- ============================== -->