Package Details: google-chrome 131.0.6778.85-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: 2247
Popularity: 8.99
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-19 19:19 (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 .. 146 147 148 149 150 151 152 153 154 155 156 157 Next › Last »

t3ddy commented on 2011-11-16 20:02 (UTC)

I could change the pkgbuild if there's a way to predict the build number automatically, so I can change the sript to read the version and modify the pkgbuild accordingly.

Det commented on 2011-11-16 18:55 (UTC)

T3ddy is already updating this thing every time someone flags it. He's just talking about not needing to change the build number when doing so.

<deleted-account> commented on 2011-11-16 18:11 (UTC)

I agree with tarpman, as that is the way PKGBUILD's are supposed to work. Even beyond that, I'm sure someone can flag it out of date if you miss an update or forget. As a maintainer, I find that's the much more easier and lazier way of doing it: only update when someone pesters me lol

t3ddy commented on 2011-11-12 20:39 (UTC)

I like your idea. The problem is that chrome gets updated very frequently, so I'm using a script to do the job. Making your change will make the script useless and increase my work. For now I won't make changes, anyway thanks for your suggestion :)

<deleted-account> commented on 2011-11-12 17:51 (UTC)

Instead of taking the current version from the direct DL link and having your md5sum fail when it changes, you could point the PKGBUILD at the versioned deb from the pool instead. e.g. http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_15.0.874.120-r108895_amd64.deb When they clean out old versions that will start to 404 (and also directory listings aren't enabled so you have to know the exact filename you want to download) but I prefer that to an md5sum failure.

<deleted-account> commented on 2011-11-10 17:28 (UTC)

Add dependencies xdg-utils becouse not open downloads folder.

Det commented on 2011-10-27 10:41 (UTC)

Or you can just check the version number to see whether it matches with the latest one: http://googlechromereleases.blogspot.com/search/label/Stable%20updates I'd prefer building with 'makepkg -si --skipinteg' anyway, since 1) the chances of getting a corrupt download from Google servers in practice are nonexistant and 2) you'd be using the md5sum of your own corrupt download anyway.

<deleted-account> commented on 2011-10-27 09:24 (UTC)

If the md5sum fails, it is probably because the *.deb package was updated. If you are certain your *.deb download is OK, you can manually replace the appropriate md5sum in the PKGBUILD or use the command posted below by nDray. Google-chrome is updated very frequently, so md5sums are difficult for the package maintainer to keep current.

Det commented on 2011-10-21 16:17 (UTC)

@massol, that's not a fix - it does the same thing. Clear out your package cache first.

« First ‹ Previous 1 .. 146 147 148 149 150 151 152 153 154 155 156 157 Next › Last »