Package Details: google-chrome 70.0.3538.67-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only)
Package Base: google-chrome
Description: The popular and trusted web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 1756
Popularity: 18.868691
First Submitted: 2010-05-25 20:25
Last Updated: 2018-10-16 22:44

Dependencies (13)

Required by (18)

Sources (3)

Pinned Comments

Det commented on 2017-10-01 00:35

The final vote. “What should be the pkgdesc of AUR/google-chrome?” With 82 votes:

● "One fast, simple, and secure browser for all your devices (Stable Channel)" - 17 votes (21%)
● "The popular and trusted web browser by Google (Stable Channel)" - 65 votes (79%)

Now, my deciding vote of 49 votes will be cast and the winner is...










..no, I’m kidding, I’m kidding. Pkgdesc changed. ^^

Det commented on 2016-03-09 05:01

✔ NOTE. If the md5sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use:

$ curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }'

For new MD5: $ curl -sL https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | sed -n '35p'

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Det commented on 2018-09-21 19:08

spicewiesel flagged google-chrome out-of-date on 2018-09-21 for the following reason:

md5 mismatch

No there isn't. Stop fake flagging.

The MD5 will only be taken from https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages

Det commented on 2018-09-18 14:14

@jimreynold2nd, at that time when you tried.

@OrdoFlammae, I don't think there is a separate mirror. That's never been an issue, and trying just now, I connect directly to CA, USA (Silicon Valley).

@frydac, when you say this took you some time, you're not serious are you?

frydac commented on 2018-09-18 08:39

It did take me a little bit of time figuring this out, so hope this helps someone. Editing the pkgbuild with following entries worked for me:

version (using the "curl ..." command in the note by Det):
69.0.3497.100

md5sum (downloading the .deb package manually and using md5sum):
1e1394cf7c75cac3f2158e812eb04393

OrdoFlammae commented on 2018-09-17 22:16

About the package being out of date, have you checked to make sure your mirror is updated?

jimreynold2nd commented on 2018-09-17 18:56

It is out of date: checksum does not match anymore.

Det commented on 2018-09-16 16:02

test1265tester flagged google-chrome out-of-date on 2018-09-16 for the following reason:

Its out of date

It isn't.

Det commented on 2018-09-12 10:14

I reviewed my pinned comment, since people just can't fathom what's going on.

sku commented on 2018-09-11 22:19

md5sum of new version „69.0.3497.92“ is „58bafb3149bb0e0d00efe61357a3bd8a“ (first line of array). To be sure this should be reviewed.

Det commented on 2018-09-05 14:47

You noobs.

uncletrunks commented on 2018-09-05 05:32

The package isn't updated yet, hence the validity check fails. Edit the PKGBUILD if you can't wait, all you've gotta do is change the version number and MD5 for the .deb file.