AU: 5 updated - veeam-one-agent veeam-one-monitor-client veeam-one-mo…

…nitor-server veeam-one-reporter-server viber [skip ci] https://gist.github.com/mkevenaar/675e3f672bda54270f8d7f5415f9374d/ea77951fb5a736bc82207e63eb20efd695904630
mkevenaar · Mar 22, 2023 · 86c341a · 86c341a
1 parent 6ac5b7e
commit 86c341a
Show file tree

Hide file tree

Showing 11 changed files with 15 additions and 15 deletions.
diff --git a/automatic/veeam-one-agent/tools/chocolateyinstall.ps1 b/automatic/veeam-one-agent/tools/chocolateyinstall.ps1
@@ -4,7 +4,7 @@ $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $isoPackageName = 'veeam-one-iso'
 $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
 $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
-$filename = 'VeeamONE_12.0.0.2498_20230125.iso'
+$filename = 'VeeamONE_12.0.1.2591_20230314.iso'
 $installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename
 
 $fileLocation = 'Agent\VeeamONE.Agent.x64.msi'

diff --git a/automatic/veeam-one-agent/veeam-one-agent.nuspec b/automatic/veeam-one-agent/veeam-one-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>12.0.0.20230125</version>
+    <version>12.0.1.20230314</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>
     <!-- ============================== -->
@@ -102,7 +102,7 @@ let them know the package is no longer updating correctly.
 
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
-      <dependency id="veeam-one-iso" version="[12.0.0.20230125]" />
+      <dependency id="veeam-one-iso" version="[12.0.1.20230314]" />
       <dependency id="chocolatey-isomount.extension" version="1.0" />
       <dependency id="DotNet4.7.2" />
     </dependencies>

diff --git a/automatic/veeam-one-monitor-client/tools/chocolateyinstall.ps1 b/automatic/veeam-one-monitor-client/tools/chocolateyinstall.ps1
@@ -4,7 +4,7 @@ $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $isoPackageName = 'veeam-one-iso'
 $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
 $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
-$filename = 'VeeamONE_12.0.0.2498_20230125.iso'
+$filename = 'VeeamONE_12.0.1.2591_20230314.iso'
 $installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename
 
 $fileLocation = 'Monitor\VeeamONE.Monitor.Client.x64.msi'

diff --git a/automatic/veeam-one-monitor-client/veeam-one-monitor-client.nuspec b/automatic/veeam-one-monitor-client/veeam-one-monitor-client.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>12.0.0.20230125</version>
+    <version>12.0.1.20230314</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>
     <!-- ============================== -->
@@ -75,7 +75,7 @@ let them know the package is no longer updating correctly.
 
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
-      <dependency id="veeam-one-iso" version="[12.0.0.20230125]" />
+      <dependency id="veeam-one-iso" version="[12.0.1.20230314]" />
       <dependency id="chocolatey-isomount.extension" version="1.0" />
       <dependency id="MSXML6.SP1" />
       <dependency id="vcredist140" />

diff --git a/automatic/veeam-one-monitor-server/tools/chocolateyinstall.ps1 b/automatic/veeam-one-monitor-server/tools/chocolateyinstall.ps1
@@ -4,7 +4,7 @@ $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $isoPackageName = 'veeam-one-iso'
 $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
 $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
-$filename = 'VeeamONE_12.0.0.2498_20230125.iso'
+$filename = 'VeeamONE_12.0.1.2591_20230314.iso'
 $installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename
 
 $fileLocation = 'Monitor\VeeamONE.Monitor.Server.x64.msi'

diff --git a/automatic/veeam-one-monitor-server/veeam-one-monitor-server.nuspec b/automatic/veeam-one-monitor-server/veeam-one-monitor-server.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>12.0.0.20230125</version>
+    <version>12.0.1.20230314</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>
     <!-- ============================== -->
@@ -84,7 +84,7 @@ let them know the package is no longer updating correctly.
 
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
-      <dependency id="veeam-one-iso" version="[12.0.0.20230125]" />
+      <dependency id="veeam-one-iso" version="[12.0.1.20230314]" />
       <dependency id="chocolatey-isomount.extension" version="1.0" />
       <dependency id="DotNet4.7.2" />
       <dependency id="vcredist140" />

diff --git a/automatic/veeam-one-reporter-server/tools/chocolateyinstall.ps1 b/automatic/veeam-one-reporter-server/tools/chocolateyinstall.ps1
@@ -4,7 +4,7 @@ $toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
 $isoPackageName = 'veeam-one-iso'
 $scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
 $commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
-$filename = 'VeeamONE_12.0.0.2498_20230125.iso'
+$filename = 'VeeamONE_12.0.1.2591_20230314.iso'
 $installPath = Join-Path  (Join-Path $commonPath $isoPackageName) $filename
 
 $fileLocation = 'Reporter\VeeamONE.Reporter.Server.x64.msi'

diff --git a/automatic/veeam-one-reporter-server/veeam-one-reporter-server.nuspec b/automatic/veeam-one-reporter-server/veeam-one-reporter-server.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>12.0.0.20230125</version>
+    <version>12.0.1.20230314</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>
     <!-- ============================== -->
@@ -82,7 +82,7 @@ let them know the package is no longer updating correctly.
 
     <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
     <dependencies>
-      <dependency id="veeam-one-iso" version="[12.0.0.20230125]" />
+      <dependency id="veeam-one-iso" version="[12.0.1.20230314]" />
       <dependency id="chocolatey-isomount.extension" version="1.0" />
       <dependency id="vcredist140" />
       <dependency id="SQL2014.SMO" />

diff --git a/automatic/viber/info b/automatic/viber/info
@@ -1 +1 @@
-"5d9d844deb7860c949e4afe1a1267f53"|19.6.0.0
+"7b8bc6f9467eb4569e032b06f10077e2"|19.7.0.2
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     = '5A1037DBCC734F5BC7A266325AC0455BCEC1C47B10655A2760F1F73AF146D7F0'
+$checksum     = 'A497C4575EC895E6907A35754024444A1AAE2B4880DC27B4D9C8AFCEEEFE13A1'
 $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>19.6.0.0</version>
+    <version>19.7.0.2</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>
     <!-- ============================== -->