Skip to content

Commit

Permalink
AU: 9 updated - veeam-backup-for-microsoft-365 veeam-backup-for-micro…
Browse files Browse the repository at this point in the history 
…soft-365-console veeam-backup-for-microsoft-365-iso veeam-backup-for-microsoft-365-management veeam-backup-for-microsoft-365-rest-api veeam-backup-for-microsoft-365-server veeam-explorer-for-microsoft-exchange-m365 veeam-explorer-for-microsoft-sharepoint-m365 veeam-explorer-for-microsoft-teams-m365

[skip ci] https://gist.github.com/675e3f672bda54270f8d7f5415f9374d/5d07bd8b8e69501cd9cb874c0571954b6da52069
  • Loading branch information
@mkevenaar
mkevenaar committed Oct 7, 2022
1 parent 76a2461 commit 68bd753
Show file tree
Hide file tree
Showing 16 changed files with 34 additions and 34 deletions.
2 changes: 1 addition & 1 deletion automatic/veeam-backup-for-microsoft-365-console/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Backup\Veeam.Backup365.msi'
Expand Down
4 changes: 2 additions & 2 deletions ...atic/veeam-backup-for-microsoft-365-console/veeam-backup-for-microsoft-365-console.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -76,7 +76,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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down
6 changes: 3 additions & 3 deletions automatic/veeam-backup-for-microsoft-365-iso/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$url = 'https://download2.veeam.com/VBO/v6/VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$checksum = 'c53ef289848c3e0fd6a2afa5de032c6ac491358420ad1c48ad6fb2cd3721b431'
$url = 'https://download2.veeam.com/VBO/v6/VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$checksum = '2154063e6ff0f9c81a30947ecb8eb40d6e951bfc1781a97e10b9a2a2bae8a45a'
$checksumType = 'sha256'

$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$packagePath = $(Split-Path -parent $toolsDir)
$installPath = Join-Path $packagePath $filename

Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-backup-for-microsoft-365-iso/veeam-backup-for-microsoft-365-iso.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down
10 changes: 5 additions & 5 deletions ...eeam-backup-for-microsoft-365-management/veeam-backup-for-microsoft-365-management.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -68,10 +68,10 @@ 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-backup-for-microsoft-365-console" version="[6.1.0.254]" />
<dependency id="veeam-explorer-for-microsoft-exchange-m365" version="[6.1.0.254]" />
<dependency id="veeam-explorer-for-microsoft-sharepoint-m365" version="[6.1.0.254]" />
<dependency id="veeam-explorer-for-microsoft-teams-m365" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.423]" />
<dependency id="veeam-explorer-for-microsoft-exchange-m365" version="[6.1.0.423]" />
<dependency id="veeam-explorer-for-microsoft-sharepoint-m365" version="[6.1.0.423]" />
<dependency id="veeam-explorer-for-microsoft-teams-m365" version="[6.1.0.423]" />
</dependencies>

<!--<provides>NOT YET IMPLEMENTED</provides>-->
Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-backup-for-microsoft-365-rest-api/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Backup\Veeam.Backup365.msi'
Expand Down
4 changes: 2 additions & 2 deletions ...ic/veeam-backup-for-microsoft-365-rest-api/veeam-backup-for-microsoft-365-rest-api.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -65,7 +65,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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-backup-for-microsoft-365-server/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Backup\Veeam.Backup365.msi'
Expand Down
4 changes: 2 additions & 2 deletions automatic/veeam-backup-for-microsoft-365-server/veeam-backup-for-microsoft-365-server.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -65,7 +65,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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down
8 changes: 4 additions & 4 deletions automatic/veeam-backup-for-microsoft-365/veeam-backup-for-microsoft-365.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -67,9 +67,9 @@ 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-backup-for-microsoft-365-server" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-rest-api" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-server" version="[6.1.0.423]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.423]" />
<dependency id="veeam-backup-for-microsoft-365-rest-api" version="[6.1.0.423]" />
</dependencies>

<!--<provides>NOT YET IMPLEMENTED</provides>-->
Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-explorer-for-microsoft-exchange-m365/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Explorers\VeeamExplorerForExchange.msi'
Expand Down
6 changes: 3 additions & 3 deletions ...am-explorer-for-microsoft-exchange-m365/veeam-explorer-for-microsoft-exchange-m365.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -61,8 +61,8 @@ 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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-explorer-for-microsoft-sharepoint-m365/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Explorers\VeeamExplorerForSharePoint.msi'
Expand Down
6 changes: 3 additions & 3 deletions ...xplorer-for-microsoft-sharepoint-m365/veeam-explorer-for-microsoft-sharepoint-m365.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -61,8 +61,8 @@ 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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down
2 changes: 1 addition & 1 deletion automatic/veeam-explorer-for-microsoft-teams-m365/tools/chocolateyinstall.ps1
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$isoPackageName = 'veeam-backup-for-microsoft-365-iso'
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$filename = 'VeeamBackupMicrosoft365_6.1.0.254_P20220825.iso'
$filename = 'VeeamBackupMicrosoft365_6.1.0.423_P20220926.iso'
$installPath = Join-Path (Join-Path $commonPath $isoPackageName) $filename

$fileLocation = 'Explorers\VeeamExplorerForTeams.msi'
Expand Down
6 changes: 3 additions & 3 deletions ...ic/veeam-explorer-for-microsoft-teams-m365/veeam-explorer-for-microsoft-teams-m365.nuspec
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,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.1.0.254</version>
<version>6.1.0.423</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>
<!-- ============================== -->
Expand Down Expand Up @@ -63,8 +63,8 @@ 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-backup-for-microsoft-365-iso" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.254]" />
<dependency id="veeam-backup-for-microsoft-365-iso" version="[6.1.0.423]" />
<dependency id="veeam-backup-for-microsoft-365-console" version="[6.1.0.423]" />
<dependency id="chocolatey-isomount.extension" version="1.0" />
<dependency id="DotNet4.7.2" />
</dependencies>
Expand Down

0 comments on commit 68bd753

Please sign in to comment.