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

[skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/02ff7c23b6c3c93e081b78b0e7300fcbacd61b4b
mkevenaar · Jan 29, 2024 · 120fbb0 · 120fbb0
1 parent 64ee094
commit 120fbb0
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.10/zabbix_agent-6.4.10-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-amd64-openssl.msi
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-windows-i386-openssl.msi
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-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: 17759F9D57CD3D310861CDD4CFC1942F42382268F39A4013017431F67976DFDB
-   checksum64: 5FB7A85DDD9D42840C964F11C482C539529FD98C801558A8A90337DBA59A102F
+   checksum32: 815E0187410E74B88314A39A7642301F3DDC00593C16799162E11D16F623BF3E
+   checksum64: 3F0C11DFDFC7FBD868E02104B970DE65167271A986081C0F9E1E3BF4788D95AC
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-amd64-openssl.msi
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-windows-i386-openssl.msi
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-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.10-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent-6.4.10-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent-6.0.26-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent-6.0.26-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,6 +1,6 @@
 {
     "6.2":  "6.2.9",
-    "6.0":  "6.0.25",
+    "6.0":  "6.0.26",
     "5.0":  "5.0.40",
     "4.0":  "4.0.50",
     "4.2":  "4.2.8",

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.10</version>
+    <version>6.0.26</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.10/zabbix_agent-6.4.10-windows-i386-openssl.zip
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-amd64-openssl.zip
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-windows-i386-openssl.zip
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-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: C7873539B5980DBE4FBC8BD15EB8A756A9FE26EA845DEF25DED49141D836C014
-   checksum64: B39FCEBB7BD0626E4EA1A33FC3421772AA8709D80E727B44519BF68423149D8D
+   checksum32: BE12228A077C95942420CB61A0BDF0F8D190EDCCBB697BDFA7A290F120C3A8DB
+   checksum64: D7ACFDF361EAE50AC42254A8C5B89CC375E25C47C45CBC60641A5DE83D125615
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-i386-openssl.zip
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent-6.4.10-windows-amd64-openssl.zip
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-windows-i386-openssl.zip
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.26/zabbix_agent-6.0.26-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.10'
+$version = '6.0.26'
 $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.10-windows-i386-openssl.zip"
-  file64        = "$toolsDir\zabbix_agent-6.4.10-windows-amd64-openssl.zip"
+  file          = "$toolsDir\zabbix_agent-6.0.26-windows-i386-openssl.zip"
+  file64        = "$toolsDir\zabbix_agent-6.0.26-windows-amd64-openssl.zip"
 }
 
 try {

diff --git a/automatic/zabbix-agent/zabbix-agent.json b/automatic/zabbix-agent/zabbix-agent.json
@@ -1,6 +1,6 @@
 {
     "6.2":  "6.2.9",
-    "6.0":  "6.0.25",
+    "6.0":  "6.0.26",
     "5.0":  "5.0.40",
     "4.0":  "4.0.50",
     "4.4":  "4.4.9",

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.10</version>
+    <version>6.0.26</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.0/6.0.25/zabbix_agent2-6.0.25-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.25/zabbix_agent2-6.0.25-windows-amd64-openssl.msi
+   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
 
    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: 2D8EE1052E3486FB26FF57E67EE3B81044C52760AD972F1EBDC76504574A99A2
-   checksum64: 702F214A92D7BB9F2902C4A904823F99E50A1BCC89EF1D3117A37A40FB3EA84E
+   checksum32: C5EEA0C2001C6675CA9271E6AE4F38DD9BD241C56A14AEF89EE61A53A8E39BC9
+   checksum64: CD85E3B0DCFFC7C282D4A9033368897526627AEDC09AF3BA6C3AF370195011CA
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.25/zabbix_agent2-6.0.25-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.0/6.0.25/zabbix_agent2-6.0.25-windows-amd64-openssl.msi
+   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
 
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.25-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent2-6.0.25-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent2-6.0.26-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent2-6.0.26-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,6 +1,6 @@
 {
     "6.2":  "6.2.9",
-    "6.0":  "6.0.25",
+    "6.0":  "6.0.26",
     "5.0":  "5.0.40",
     "5.2":  "5.2.7",
     "5.4":  "5.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.0.25</version>
+    <version>6.0.26</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>
     <!-- ============================== -->