AU: 1 updated - zabbix-agent2

[skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/a1266d57ee585faf89c8c76c6739e8add20de9e7
mkevenaar · Jan 29, 2024 · 130fe77 · 130fe77
1 parent 8d95eac
commit 130fe77
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
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.0/6.0.26/zabbix_agent2-6.0.26-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent2-6.0.26-windows-amd64-openssl.msi
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.41/zabbix_agent2-5.0.41-windows-i386-openssl.msi
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.41/zabbix_agent2-5.0.41-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: C5EEA0C2001C6675CA9271E6AE4F38DD9BD241C56A14AEF89EE61A53A8E39BC9
-   checksum64: CD85E3B0DCFFC7C282D4A9033368897526627AEDC09AF3BA6C3AF370195011CA
+   checksum32: AC0519F2B96E893FB077322E8931D46847E067D6B3BD29D77E1F6A3E3AC70FD1
+   checksum64: 7BA19A893F23C436AD4CCD09936F5784F25EA4A8FA054BC045235B6B49C13BAF
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent2-6.0.26-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent2-6.0.26-windows-amd64-openssl.msi
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.41/zabbix_agent2-5.0.41-windows-i386-openssl.msi
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/5.0/5.0.41/zabbix_agent2-5.0.41-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.0.26-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent2-6.0.26-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent2-5.0.41-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent2-5.0.41-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.26",
-    "5.0":  "5.0.40",
+    "5.0":  "5.0.41",
     "5.2":  "5.2.7",
     "5.4":  "5.4.12",
     "6.4":  "6.4.10"

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.0.26</version>
+    <version>5.0.41</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>
     <!-- ============================== -->