Notices: This section not yet converted to new layout. Download stats are rolling back out.

Google Chrome Canary Web Browser

Package test results are passing.

This package was rejected on 5/10/2019. The reviewer chocolatey-ops has listed the following reason(s):

thempb (maintainer) on 04 Apr 2019 05:28:32 +00:00:

User 'thempb' (maintainer) submitted package.

chocolatey-ops (reviewer) on 04 Apr 2019 06:00:02 +00:00:

GoogleChrome.Canary has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

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 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...
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 id includes dots (.). Usually the package id is separated by '-' instead of dots (except in the case of *.install and *.portable). The reviewer will ensure this is not a new package. More...

chocolatey-ops (reviewer) on 04 Apr 2019 06:32:02 +00:00:

GoogleChrome.Canary has passed 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/20eeb50d774353c7dcc3d3f9538def3c for details.
This is an FYI only. There is no action you need to take.

Pauby (reviewer) on 05 Apr 2019 15:56:04 +00:00:

Please see the comments on v75.0.0 as they are still relevant.

Can I ask you NOT to push any further versions until you have resolved the issues with the current ones?

chocolatey-ops (reviewer) on 25 Apr 2019 15:59:50 +00:00:

We've found GoogleChrome.Canary v75.0.3 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 10 May 2019 16:03:12 +00:00:

Unfortunately there has not been progress to move GoogleChrome.Canary v75.0.3 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'.


Not for the faint of heart
Canary is designed for developers and early adopters, and can sometimes break down completely.
Nightly updates
Canary changes almost every day.
Side-by-side install
Run Canary and Chrome Stable at the same time.

Note that Chrome auto-updates itself after an initial install.

Files

Hide
  • tools\chocolateyInstall.ps1 Show
    $package = 'Chrome.Canary'
    
    try {
    
      function Get-CurrentDirectory
      {
        $thisName = $MyInvocation.MyCommand.Name
        [IO.Path]::GetDirectoryName((Get-Content function:$thisName).File)
      }
    
      . (Join-Path (Get-CurrentDirectory) 'ChromeHelpers.ps1')
    
      $installedPath = Get-ChromePath -Canary
      if (Test-Path $installedPath)
      {
        Write-Host "Chrome Canary already installed at $installedPath"
      }
      else
      {
       if([System.Environment]::Is64BitOperatingSystem)
       {
        $url = 'https://dl.google.com/tag/s/appguid%3D%7B4EA16AC7-FD5A-47C3-875B-DBF4A2008C20%7D%26iid%3D%7B930C9E9E-6131-19D5-6D03-EEE4BD9BF2EC%7D%26lang%3Diw%26browser%3D4%26usagestats%3D1%26appname%3DGoogle%2520Chrome%2520Canary%26needsadmin%3Dfalse%26ap%3Dx64-canary-statsdef_1%26installdataindex%3Dempty/update2/installers/ChromeSetup.exe'
       }
       else
       {
        $url = 'https://dl.google.com/tag/s/appguid%3D%7B4ea16ac7-fd5a-47c3-875b-dbf4a2008c20%7D%26iid%3D%7B0281A7E2-6043-D983-8BBA-7FD622493C9D%7D%26lang%3Den%26browser%3D4%26usagestats%3D1%26appname%3DGoogle%2520Chrome%2520Canary%26needsadmin%3Dfalse/update2/installers/ChromeSetup.exe'
       }
       
        Install-ChocolateyPackage 'ChromeSetup' 'exe' '/silent /install' $url
      }
    
    }
    catch {
      throw
    }
    
  • tools\ChromeHelpers.ps1 Show
    function Get-ChromePath
    {
      [CmdletBinding()]
      param(
        [Parameter(Mandatory = $false)]
        [Switch]
        $Canary = $false
      )
    
      $path = if ($Canary) { 'Google\Chrome SxS' } else { 'Google\Chrome' }
    
      Join-Path $Env:LOCALAPPDATA $path
    }
    
    function Get-ChromeExtensions
    {
      [CmdletBinding()]
      param(
        [Parameter(Mandatory = $false)]
        [Switch]
        $Canary = $false,
    
        [Parameter(Mandatory = $false)]
        [bool]
        $ExcludeBlacklist = $true
      )
    
      $installed = @{}
    
      $root = Get-ChromePath -Canary:$Canary
      $prefsPath = Join-Path $root 'User Data\Default\Preferences'
    
      if (Test-Path $prefsPath)
      {
        Write-Verbose "Examining $prefsPath for installed extensions...`n`n"
        $prefs = ConvertFrom-Json ([IO.File]::ReadAllText($prefsPath))
    
        $prefs.extensions.settings.PsObject.Properties |
          ? { if ($ExcludeBlacklist) { -not $_.Value.blacklist } else { $true } } |
          % {
             $installed[$_.Name] = $_.Value
             $msg = "Found Extension $($_.Value.manifest.name) [$($_.Name)]"
             if (!$ExcludeBlacklist -and $_.Value.blacklist)
             {
              $msg += " - Blacklist [$($_.Value.blacklist)]"
            }
             Write-Verbose $msg
          }
      }
    
      return $installed
    }
    
    # this is a bit of a misnomer, it just finds and launches Chrome with
    # new tabs for each extension since the end user still has to click a button
    function Install-ChromeExtensions
    {
      [CmdletBinding()]
      param(
        [Parameter(Mandatory = $false)]
        [Switch]
        $Canary = $false,
    
        [Parameter(Mandatory = $true)]
        [Hashtable]
        $Extensions
        # Expected a hash of Id / Name
      )
    
      $name = 'Chrome'
      if ($Canary) { $name += ' Canary'}
    
      $installed = Get-ChromeExtensions -Canary:$Canary
      $rootPath = Get-ChromePath -Canary:$Canary
      $chromeExe = Join-Path $rootPath 'Application\chrome.exe'
    
      $Extensions.GetEnumerator() |
        ? { $installed.Keys -contains $_.Key } |
        % {
          Write-Verbose "$name Extension $($_.Value) [$($_.Key)] is already installed!"
        }
    
      $storeUrl = 'https://chrome.google.com/webstore/detail'
      $chromeParams = @()
      $neededPackages = $Extensions.GetEnumerator() |
        ? { $installed.Keys -notcontains $_.Key } |
        % {
          Write-Host "Launching $name to install extension $($_.Value) [$($_.Key)]!"
          # http://peter.sh/experiments/chromium-command-line-switches/
          $chromeParams += "--new-window", "$storeUrl/$($_.Key)"
        }
    
      if ($chromeParams.Count -gt 0)
      {
        Write-Host "`n`nExecuting $chromeExe $chromeParams"
        &$chromeExe @chromeParams
      }
      else
      {
        Write-Host "`n`nAll extensions already installed!"
      }
    }
    

Virus Scan Results

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.

Dependencies

This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Google

Tags

Version History

Version Downloads Last updated Status
Google Chrome Canary Web Browser 24.0.1300.0 528 Thursday, October 18, 2012  

Discussion for the Google Chrome Canary Web Browser Package

Ground rules:

  • This discussion is only about Google Chrome Canary Web Browser and the Google Chrome Canary Web Browser 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.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Google Chrome Canary Web Browser, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

comments powered by Disqus
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok