#### chrome (Install)

61

61

Maintainer(s):

Software Author(s):

• __REPLACE_AUTHORS_OF_SOFTWARE_COMMA_SEPARATED__
• 1
• 2
• 3

### Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Failed

Verification Testing Failed

Details

Scan Testing Successful:

No detections found in any package files

Details

This package was rejected on 02 Oct 2020. The reviewer chocolatey-ops has listed the following reason(s):

#### canzhh (maintainer) on 24 Aug 2020 13:56:06 +00:00:

User 'canzhh' (maintainer) submitted package.

#### chocolatey-ops (reviewer) on 24 Aug 2020 14:28:14 +00:00:

chrome has failed automated validation.

##### Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

• The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
• Comments from template should be cleaned up and removed. More...
• Nuspec file contains templated values which should be removed. More...
##### Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

• The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
• The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
• The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
• Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
• Description should be sufficient to explain the software. Please fill in the description with more information about the software. Feel free to use use markdown. More...
##### Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

• The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
• docsUrl - points to the location of the wiki or docs of the software
• mailingListUrl - points to the forum or email list group for the software
• bugTrackerUrl - points to the location where issues and tickets can be accessed
• projectSourceUrl - points to the location of the underlying software source
##### Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

• The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

#### chocolatey-ops (reviewer) on 28 Aug 2020 21:45:59 +00:00:

chrome has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/a55da98ce3364303ea6b9b1ac886e2bb for details.
The package status will be changed and will be waiting on your next actions.

• NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
• Please log in and leave a review comment if you have questions and/or comments.
• If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
• If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
• Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
• A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

#### chocolatey-ops (reviewer) on 17 Sep 2020 21:50:01 +00:00:

We've found chrome v84.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

• Log in to the site and respond to the review comments.
• Resubmit fixes for this version.
• If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

#### chocolatey-ops (reviewer) on 02 Oct 2020 21:52:44 +00:00:

Unfortunately there has not been progress to move chrome v84.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

__REPLACE__MarkDown_Okay

tools\chocolateybeforemodify.ps1
# This runs in 0.9.10+ before upgrade and uninstall.
# Use this file to do things like stop services prior to upgrade or uninstall.
# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you
#  need to uninstall an MSI prior to upgrade, put the functionality in this
#  file without calling the uninstall script. Make it idempotent in the
#  uninstall script so that it doesn't fail when it is already uninstalled.
# NOTE: For upgrades - like the uninstall script, this script always runs from
#  the currently installed version, not from the new upgraded package version.


tools\chocolateyinstall.ps1
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
#   $f='c:\path\to\thisFile.ps1' # gc$f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File$f+".~" -en utf8; mv -fo $f+".~"$f

# 1. See the _TODO.md that is generated top level and read through that
# 2. Follow the documentation below to learn how to create a package for the package type you are creating.
# 3. In Chocolatey scripts, ALWAYS use absolute paths - $toolsDir gets you to the package's tools directory.$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" # Internal packages (organizations) or software that has redistribution rights (community repo) # - Use Install-ChocolateyInstallPackage instead of Install-ChocolateyPackage # and put the binaries directly into the tools folder (we call it embedding) #$fileLocation = Join-Path $toolsDir 'NAME_OF_EMBEDDED_INSTALLER_FILE' # If embedding binaries increase total nupkg size to over 1GB, use share location or download from urls #$fileLocation = '\\SHARE_LOCATION\to\INSTALLER_FILE'
# Community Repo: Use official urls for non-redist binaries or redist where total package size is over 200MB
# Internal/Organization: Download from internal location (internet sources are unreliable)
$url = '' # download url, HTTPS preferred$url64      = '' # 64bit URL here (HTTPS preferred) or remove - if installer contains both (very rare), use $url$packageArgs = @{
packageName   = $env:ChocolateyPackageName unzipLocation =$toolsDir
fileType      = 'EXE_MSI_OR_MSU' #only one of these: exe, msi, msu
url           = $url url64bit =$url64
#file         = $fileLocation softwareName = 'chrome*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique # Checksums are now required as of 0.10.0. # To determine checksums, you can get that from the original site if provided. # You can also use checksum.exe (choco install checksum) and use it # e.g. checksum -t sha256 -f path\to\file checksum = '' checksumType = 'sha256' #default is md5, can also be sha1, sha256 or sha512 checksum64 = '' checksumType64= 'sha256' #default is checksumType # MSI silentArgs = "/qn /norestart /l*v "$($env:TEMP)\$($packageName).$($env:chocolateyPackageVersion).MsiInstall.log"" # ALLUSERS=1 DISABLEDESKTOPSHORTCUT=1 ADDDESKTOPICON=0 ADDSTARTMENU=0 validExitCodes= @(0, 3010, 1641) # OTHERS # Uncomment matching EXE type (sorted by most to least common) #silentArgs = '/S' # NSIS #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup #silentArgs = '/s' # InstallShield #silentArgs = '/s /v"/qn"' # InstallShield with MSI #silentArgs = '/s' # Wise InstallMaster #silentArgs = '-s' # Squirrel #silentArgs = '-q' # Install4j #silentArgs = '-s' # Ghost # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) # https://chocolatey.org/packages/autohotkey.portable #validExitCodes= @(0) #please insert other valid exit codes here } Install-ChocolateyPackage @packageArgs # https://chocolatey.org/docs/helpers-install-chocolatey-package #Install-ChocolateyZipPackage @packageArgs # https://chocolatey.org/docs/helpers-install-chocolatey-zip-package ## If you are making your own internal packages (organizations), you can embed the installer or ## put on internal file share and use the following instead (you'll need to add$file to the above)
#Install-ChocolateyInstallPackage @packageArgs # https://chocolatey.org/docs/helpers-install-chocolatey-install-package

## Main helper functions - these have error handling tucked into them already
## see https://chocolatey.org/docs/helpers-reference

## Install an application, will assert administrative rights
## - https://chocolatey.org/docs/helpers-install-chocolatey-package
## - https://chocolatey.org/docs/helpers-install-chocolatey-install-package
## add additional optional arguments as necessary
##Install-ChocolateyPackage $packageName$fileType $silentArgs$url [$url64 -validExitCodes$validExitCodes -checksum $checksum -checksumType$checksumType -checksum64 $checksum64 -checksumType64$checksumType64]

## Download and unpack a zip file - https://chocolatey.org/docs/helpers-install-chocolatey-zip-package
##Install-ChocolateyZipPackage $packageName$url $toolsDir [$url64 -checksum $checksum -checksumType$checksumType -checksum64 $checksum64 -checksumType64$checksumType64]

## Install Visual Studio Package - https://chocolatey.org/docs/helpers-install-chocolatey-vsix-package
#Install-ChocolateyVsixPackage $packageName$url [$vsVersion] [-checksum$checksum -checksumType $checksumType] #Install-ChocolateyVsixPackage @packageArgs ## see the full list at https://chocolatey.org/docs/helpers-reference ## downloader that the main helpers use to download items ## if removing$url64, please remove from here
## - https://chocolatey.org/docs/helpers-get-chocolatey-web-file
#Get-ChocolateyWebFile $packageName 'DOWNLOAD_TO_FILE_FULL_PATH'$url $url64 ## Installer, will assert administrative rights - used by Install-ChocolateyPackage ## use this for embedding installers in the package when not going to community feed or when you have distribution rights ## - https://chocolatey.org/docs/helpers-install-chocolatey-install-package #Install-ChocolateyInstallPackage$packageName $fileType$silentArgs '_FULLFILEPATH_' -validExitCodes $validExitCodes ## Unzips a file to the specified location - auto overwrites existing content ## - https://chocolatey.org/docs/helpers-get-chocolatey-unzip #Get-ChocolateyUnzip "FULL_LOCATION_TO_ZIP.zip"$toolsDir

## Runs processes asserting UAC, will assert administrative rights - used by Install-ChocolateyInstallPackage
#Start-ChocolateyProcessAsAdmin 'STATEMENTS_TO_RUN' 'Optional_Application_If_Not_PowerShell' -validExitCodes $validExitCodes ## To avoid quoting issues, you can also assemble your -Statements in another variable and pass it in #$appPath = "$env:ProgramFiles\appname" ##Will resolve to C:\Program Files\appname #$statementsToRun = "/C "$appPath\bin\installservice.bat"" #Start-ChocolateyProcessAsAdmin$statementsToRun cmd -validExitCodes $validExitCodes ## add specific folders to the path - any executables found in the chocolatey package ## folder will already be on the path. This is used in addition to that or for cases ## when a native installer doesn't add things to the path. ## - https://chocolatey.org/docs/helpers-install-chocolatey-path #Install-ChocolateyPath 'LOCATION_TO_ADD_TO_PATH' 'User_OR_Machine' # Machine will assert administrative rights ## Add specific files as shortcuts to the desktop ## - https://chocolatey.org/docs/helpers-install-chocolatey-shortcut #$target = Join-Path $toolsDir "$($packageName).exe" # Install-ChocolateyShortcut -shortcutFilePath "<path>" -targetPath "<path>" [-workDirectory "C:\" -arguments "C:\test.txt" -iconLocation "C:\test.ico" -description "This is the description"] ## Outputs the bitness of the OS (either "32" or "64") ## - https://chocolatey.org/docs/helpers-get-o-s-architecture-width #$osBitness = Get-ProcessorBits

## Set persistent Environment variables
## - https://chocolatey.org/docs/helpers-install-chocolatey-environment-variable
#Install-ChocolateyEnvironmentVariable -variableName "SOMEVAR" -variableValue "value" [-variableType = 'Machine' #Defaults to 'User']

## Set up a file association
## - https://chocolatey.org/docs/helpers-install-chocolatey-file-association
#Install-ChocolateyFileAssociation

## Adding a shim when not automatically found - Cocolatey automatically shims exe files found in package directory.
## - https://chocolatey.org/docs/helpers-install-bin-file
## - https://chocolatey.org/docs/create-packages#how-do-i-exclude-executables-from-getting-shims
#Install-BinFile

##PORTABLE EXAMPLE
#$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" # despite the name "Install-ChocolateyZipPackage" this also works with 7z archives #Install-ChocolateyZipPackage$packageName $url$toolsDir $url64 ## END PORTABLE EXAMPLE ## [DEPRECATING] PORTABLE EXAMPLE #$binRoot = Get-BinRoot
#$installDir = Join-Path$binRoot "$packageName" #Write-Host "Adding '$installDir' to the path and the current shell path"
#Install-ChocolateyPath "$installDir" #$env:Path = "$($env:Path);$installDir" # if removing$url64, please remove from here
# despite the name "Install-ChocolateyZipPackage" this also works with 7z archives
#Install-ChocolateyZipPackage "$packageName" "$url" "$installDir" "$url64"
## END PORTABLE EXAMPLE

tools\chocolateyuninstall.ps1
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
#   $f='c:\path\to\thisFile.ps1' # gc$f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File$f+".~" -en utf8; mv -fo $f+".~"$f

## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements),
## AutoUninstaller should be able to detect and handle registry uninstalls without a chocolateyUninstall.ps1.
## See https://chocolatey.org/docs/commands-uninstall
## and https://chocolatey.org/docs/helpers-uninstall-chocolatey-package

## If this is an MSI, ensure 'softwareName' is appropriate, then clean up comments and you are done.
## If this is an exe, change fileType, silentArgs, and validExitCodes

$ErrorActionPreference = 'Stop'; # stop on all errors$packageArgs = @{
packageName   = $env:ChocolateyPackageName softwareName = 'chrome*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique fileType = 'EXE_MSI_OR_MSU' #only one of these: MSI or EXE (ignore MSU for now) # MSI silentArgs = "/qn /norestart" validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx # OTHERS # Uncomment matching EXE type (sorted by most to least common) #silentArgs = '/S' # NSIS #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup #silentArgs = '/s' # InstallShield #silentArgs = '/s /v"/qn"' # InstallShield with MSI #silentArgs = '/s' # Wise InstallMaster #silentArgs = '-s' # Squirrel #silentArgs = '-q' # Install4j #silentArgs = '-s -u' # Ghost # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) # https://chocolatey.org/packages/autohotkey.portable #validExitCodes= @(0) #please insert other valid exit codes here }$uninstalled = $false # Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below, # take a dependency on "chocolatey-core.extension" in your nuspec file. # This is only a fuzzy search if$softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[array]$key = Get-UninstallRegistryKey -SoftwareName$packageArgs['softwareName']

if ($key.Count -eq 1) {$key | % {
$packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below if ($packageArgs['fileType'] -eq 'MSI') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$packageArgs['silentArgs'] = "$($_.PSChildName)$($packageArgs['silentArgs'])" # Don't pass anything for file, it is ignored for msi (facepalm number 2) # Alternatively if you need to pass a path to an msi, determine that and # use it instead of the above in silentArgs, still very first$packageArgs['file'] = ''
} else {
# NOTES:
# - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats # - Split args from exe in$packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them # - Ensure you don't pass double quotes in$file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this" # - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192 } Uninstall-ChocolateyPackage @packageArgs } } elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means." } elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "-$($_.DisplayName)"} } ## OTHER POWERSHELL FUNCTIONS ## https://chocolatey.org/docs/helpers-reference #Uninstall-ChocolateyZipPackage$packageName # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
## Remove any shortcuts you added in the install script.



Note: Include this file if including binaries you have the right to distribute.
Otherwise delete. this file.

===DELETE ABOVE THIS LINE AND THIS LINE===

From: <insert applicable license url here>


tools\VERIFICATION.txt

Note: Include this file if including binaries you have the right to distribute.
Otherwise delete. this file. If you are the software author, you can change this
mention you are the author of the software.

===DELETE ABOVE THIS LINE AND THIS LINE===

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

<Include details of how to verify checksum contents>
<If software vendor, explain that here - checksum verification instructions are optional>

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

This package has no dependencies.

Discussion for the chrome (Install) Package

### Ground Rules:

• This discussion is only about chrome (Install) and the chrome (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
• This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.