Skip to content

Commit

Permalink
AU: 2 updated - crystaldiskinfo crystaldiskinfo.install
Browse files Browse the repository at this point in the history
  • Loading branch information
mkevenaar committed Oct 22, 2021
1 parent b12f1f3 commit ff0f3fc
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
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>8.12.10</version>
<version>8.12.11</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
4 changes: 2 additions & 2 deletions automatic/crystaldiskinfo.install/legal/VERIFICATION.txt
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,12 @@ The installer have been downloaded from their official download link listed on <
and can be verified like this:

1. Download the following installers:
32-Bit: <https://free.nchc.org.tw/osdn//crystaldiskinfo/76150/CrystalDiskInfo8_12_10.exe>
32-Bit: <https://osdn.dl.osdn.net/crystaldiskinfo/76208/CrystalDiskInfo8_12_11.exe>
2. You can use one of the following methods to obtain the checksum
- Use powershell function 'Get-Filehash'
- Use chocolatey utility 'checksum.exe'

checksum type: sha256
checksum32: 5174FB7EA78F72BB4D4EB048326D1028CFFF6D2AEEB0AF88B079E2593B44F819
checksum32: 37ABE4AA0143AB8DC0D5F9C20220C0EF2B042983B5B5D338AA039C7A7FA6FC47

File 'LICENSE.txt' is obtained from <https://github.com/hiyohiyo/CrystalDiskInfo/blob/master/LICENSE.txt>
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ $toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
fileType = 'exe'
file = "$toolsDir\CrystalDiskInfo8_12_10.exe"
file = "$toolsDir\CrystalDiskInfo8_12_11.exe"
softwareName = 'Crystaldiskinfo*'
silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
validExitCodes= @(0)
Expand Down
4 changes: 2 additions & 2 deletions automatic/crystaldiskinfo/crystaldiskinfo.nuspec
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>8.12.10</version>
<version>8.12.11</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,7 +61,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="crystaldiskinfo.portable" version="[8.12.10]" />
<dependency id="crystaldiskinfo.portable" version="[8.12.11]" />
</dependencies>

<!--<provides>NOT YET IMPLEMENTED</provides>-->
Expand Down

0 comments on commit ff0f3fc

Please sign in to comment.