Package Details: google-chrome 132.0.6834.159-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: 2258
Popularity: 8.70
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-01-28 23:25 (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 .. 126 127 128 129 130 131 132 133 134 135 136 .. 157 Next › Last »

Det commented on 2013-03-14 12:35 (UTC)

Uhhh.. you're asking how can the _current_ url get the pkgver the same way the versioned one does? Well, you find it out first the same way it's done now, silly. What did you think the current solution is some ungreppable magic that automatically updates itself :D? If you're asking what to do with the local one that's already there (since it's gonna have the same name), then you do a: source=("google-chrome-${_channel}_${pkgver}_${_arch}.rpm"::"http(s)://dl.google.com/dl/linux/direct/google-chrome-${_channel}_current_${_arch}.rpm") Which has the only downside that it's very fugly and renders the Source text up there to just "google-chrome-${_channel}_${pkgver}_${_arch}.rpm", as in with google-earth (still points to the real file, though).

<deleted-account> commented on 2013-03-14 12:16 (UTC)

@Det: Thanks! But what I meant is how does a script know that it has to update a local Google Chrome version to a newer one from the internet? It can't read that blog...

Det commented on 2013-03-14 00:48 (UTC)

@distronicon: http://googlechromereleases.blogspot.com/

<deleted-account> commented on 2013-03-13 18:56 (UTC)

@mdyan: Agree. @XenGi: How do you know what version you download exactly when you get something from "...current..."?

mdyan commented on 2013-03-13 17:25 (UTC)

I don't mean to speak for the package maintainer, but I think that it's for versioning purposes.

XenGi commented on 2013-03-13 14:11 (UTC)

Why not using the link to the latest stable instead of building the url from some blog posting? https://dl.google.com/linux/direct/google-chrome-stable_current_$arch.rpm Where $arch is x86_64 or i386.

<deleted-account> commented on 2013-03-13 09:43 (UTC)

http://dl.google.com/linux/chrome/rpm/stable/x86_64/google-chrome-stable-25.0.1364.160-186726.x86_64.rpm seems to be invalid, too :(

Det commented on 2013-03-11 17:58 (UTC)

I think it was due to Xorg 1.14.

TheWretched commented on 2013-03-11 17:53 (UTC)

For what it's worth, version 25.0.1364.160-1 seems to work a lot better on kde 4.10 for me having updated to it this morning. I haven't got the middle click = messed up tab + browser freezing issue so far. Knock on wood.

mfs commented on 2013-03-08 10:29 (UTC)

The stable_current_x86_64 is already 25.0.1364.160.

« First ‹ Previous 1 .. 126 127 128 129 130 131 132 133 134 135 136 .. 157 Next › Last »