Package Details: google-chrome 130.0.6723.116-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2243
Popularity: 7.15
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-05 19:02 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 106 107 108 109 110 111 112 113 114 115 116 .. 157 Next › Last »

Det commented on 2014-02-20 23:22 (UTC)

Yeah, I know they have concerns, but it's not the end of the world and something everybody has to comment on. You flag it once, and it won't be updated any faster no matter how many times you wonder why it doesn't match.

Archwyrm commented on 2014-02-20 23:14 (UTC)

Det: I ran into the md5sum issue with the older google-chrome-stable_32.0.1700.107_amd64.deb so perhaps others had some concern along those lines. Personally, since the file name was the same and only the md5sum differed, I decided to play things safe and wait for an update. Only had to wait a day. Thank you for your efforts! :) A little patience goes a long way..

mike.cloaked commented on 2014-02-20 21:57 (UTC)

Only seconds after I looked it was already fixed... thank you Det (I presume).

mike.cloaked commented on 2014-02-20 21:53 (UTC)

It is simple to edit the PKGBUILD file with the new md5sums - but also you need to change the build number to end in 117 - the current file ends in 115. Other than that it is fine.

Det commented on 2014-02-20 21:47 (UTC)

I can't believe you guys raise such a fuzz about an outdated PKGBUILD.

rikless commented on 2014-02-20 19:47 (UTC)

concerns by FadeMind issue too.

FadeMind commented on 2014-02-20 19:10 (UTC)

Today Google released second update of Google Chrome. Current version is 33.0.1750.117 Correct MD5SUMS: $ md5sum google-chrome-stable_33.0.1750.117_i386.deb 8159f0484cf3fab3e768d1665aa58871 google-chrome-stable_33.0.1750.117_i386.deb $ md5sum google-chrome-stable_33.0.1750.117_amd64.deb a5c986f948ca72db015236fb9b6bb986 google-chrome-stable_33.0.1750.117_amd64.deb PKGBUILD MD5SUM CORRECT: md5sums=('8159f0484cf3fab3e768d1665aa58871' 'ba19ea498f294975d320ff0b26a6cd63') [ "$CARCH" = 'x86_64' ] && md5sums[0]='a5c986f948ca72db015236fb9b6bb986' AUR now have outdated data in PKGBUILD file.

A.J commented on 2014-02-20 18:50 (UTC)

the stable channel is at 33.0.1750.117 ??!

keepitsimpleengr commented on 2014-02-20 17:58 (UTC)

anybody know the md5sums for google-chrome 32bit ?

silent commented on 2014-02-20 17:29 (UTC)

md5sums for google-chrome amd64 Version 33.0.1750.117 should be 'a5c986f948ca72db015236fb9b6bb986'

« First ‹ Previous 1 .. 106 107 108 109 110 111 112 113 114 115 116 .. 157 Next › Last »