Package Details: google-chrome 129.0.6668.58-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: 2236
Popularity: 7.19
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (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 .. 41 42 43 44 45 46 47 48 49 50 51 .. 157 Next › Last »

OrdoFlammae commented on 2018-09-17 22:16 (UTC)

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 (UTC)

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

Det commented on 2018-09-16 16:02 (UTC)

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 (UTC) (edited on 2018-09-12 20:47 (UTC) by Det)

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

sku commented on 2018-09-11 22:19 (UTC)

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 (UTC)

You noobs.

uncletrunks commented on 2018-09-05 05:32 (UTC)

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.

riemannrocker commented on 2018-09-05 04:45 (UTC)

Another case of "One or more files did not pass the validity check!"

st8plgun commented on 2018-09-05 03:04 (UTC)

I'm getting the same error... "one or more files did not pass the validity check"

« First ‹ Previous 1 .. 41 42 43 44 45 46 47 48 49 50 51 .. 157 Next › Last »