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: 2248
Popularity: 10.09
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 .. 73 74 75 76 77 78 79 80 81 82 83 .. 157 Next › Last »

Det commented on 2016-02-04 06:56 (UTC)

I'm not aware of Chrome automatically updating itself, besides on OS X, Windows, and Ubuntu (adds itself to /etc/apt/sources.list.d/).

eduncan911 commented on 2016-02-04 06:43 (UTC)

Here's a question: Does one need to keep updating this AUR package? Chrome self-updates to newer versions (when I installed it manually before). Or, does this package disable the auto-updating part of Chrome so that one must always keep this AUR package up to date?

Det commented on 2015-12-31 03:33 (UTC) (edited on 2016-01-23 20:52 (UTC) by Det)

That's good if they should be up-to-date as well, but there were enough people without one for me to just put the version number up there. In-and-of-itself, you don't do much with a PKGBUILD without pacman.

markzz commented on 2015-12-30 23:19 (UTC) (edited on 2015-12-30 23:21 (UTC) by markzz)

Any package belonging to the base (pacman is in base) or base-devel group are assumed to be installed and up to date on their systems before running makepkg, so adding pacman to the makedepends is redundant and unneeded.

Det commented on 2015-12-30 01:19 (UTC)

@markzz, "and the PKGBUILD doesn't appear to need any extra things from a specific version of pacman." Except it does actually quite clearly :D. "source_$CARCH" and "md5sums_$CARCH" were both features of makedepends=('pacman>=4.2.0').

markzz commented on 2015-12-29 23:20 (UTC) (edited on 2015-12-29 23:23 (UTC) by markzz)

Why is pacman a makedepends? It shouldn't be there because pacman is assumed to be installed on the system and the PKGBUILD doesn't appear to need any extra things from a specific version of pacman.

Det commented on 2015-12-24 16:37 (UTC)

The license prevents it: https://www.google.com/chrome/browser/privacy/eula_text.html

tago commented on 2015-12-24 16:31 (UTC)

Why is not on official rep?

Det commented on 2015-12-12 11:14 (UTC)

Yeah, these are Google binaries and builds for Ubuntu/Debian, which I have no authority over whatsoever. But like the announcement says, the old ABI is still available.

catalin.hritcu commented on 2015-12-12 11:11 (UTC)

This package shows up on the list of packages that need to be rebuit after the recent switch to C++ dual ABI. https://lists.archlinux.org/pipermail/arch-dev-public/2015-December/027597.html Since this package seems directly based on Google binaries this will might need to be escalated with Google if that wasn't done already.

« First ‹ Previous 1 .. 73 74 75 76 77 78 79 80 81 82 83 .. 157 Next › Last »