AU: 2 updated - viber zabbix-agent2

[skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/8542963f0bec85be6b6304d136fb316d070cf339
mkevenaar · Dec 13, 2023 · 25865d0 · 25865d0
1 parent 1b3c636
commit 25865d0
Show file tree

Hide file tree

Showing 7 changed files with 13 additions and 13 deletions.
diff --git a/automatic/viber/info b/automatic/viber/info
@@ -1 +1 @@
-"510fc0e4d394c4389b35b4b4baa15603"|21.5.0.3
+"2bffa24676e644482c652b6717477e2f"|21.6.0.0
diff --git a/automatic/viber/tools/chocolateyInstall.ps1 b/automatic/viber/tools/chocolateyInstall.ps1
@@ -2,7 +2,7 @@
 
 $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $url          = 'https://download.cdn.viber.com/desktop/windows/ViberSetup.exe'
-$checksum     = '01DA84EE0BE03DEC02401D5E670DE7CCBB24A67AE023AFEDE78ADA78CD7E2BCC'
+$checksum     = 'A2A4C41860D21C76FC70D5831FE7AFAACBCA9E85CBCE3464421AABD673AD3F9E'
 $checksumType = 'sha256'
 $packageArgs = @{
   packageName    = $env:ChocolateyPackageName

diff --git a/automatic/viber/viber.nuspec b/automatic/viber/viber.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>21.5.0.3</version>
+    <version>21.6.0.0</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.9/zabbix_agent2-6.4.9-windows-i386-openssl.msi
-   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.9/zabbix_agent2-6.4.9-windows-amd64-openssl.msi
+   x32 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent2-6.4.10-windows-i386-openssl.msi
+   x64 url: https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent2-6.4.10-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: 8631E606D2BF9D192A12222EBF260130BA0C2E829D7C8CFF956EC1008BD4EC0B
-   checksum64: 0FF8F404D0C1F3C7A0A956A43B250A5BAF3BB569867401DF2888E3A1B3B285A1
+   checksum32: 69BD6443507ED02A042CBA20E393E9E9620BC610A09A75C7A211106E35BC960A
+   checksum64: 2DBA1E3A3CB8DF028B7EE83AD4A994C296AD90725BB900DC2DA07B975C439D7E
 
 Using AU:
 
-   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.9/zabbix_agent2-6.4.9-windows-i386-openssl.msi
-   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.9/zabbix_agent2-6.4.9-windows-amd64-openssl.msi
+   x32: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent2-6.4.10-windows-i386-openssl.msi
+   x64: Get-RemoteChecksum https://cdn.zabbix.com/zabbix/binaries/stable/6.4/6.4.10/zabbix_agent2-6.4.10-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.9-windows-i386-openssl.msi"
-  file64        = "$toolsDir\zabbix_agent2-6.4.9-windows-amd64-openssl.msi"
+  file          = "$toolsDir\zabbix_agent2-6.4.10-windows-i386-openssl.msi"
+  file64        = "$toolsDir\zabbix_agent2-6.4.10-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
@@ -4,5 +4,5 @@
     "5.0":  "5.0.40",
     "5.2":  "5.2.7",
     "5.4":  "5.4.12",
-    "6.4":  "6.4.9"
+    "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.4.9</version>
+    <version>6.4.10</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>
     <!-- ============================== -->