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

ruario commented on 2012-01-09 09:25 (UTC)

@DetYes, apologies. I thought of each improvement a bit at a time. I wasn't international spamming. Anyway I don't think the idea would be to put it in the PKGBUILD itself. t3ddy said, "The problem is that chrome gets updated very frequently, so I'm using a script to do the job." I read that as him having some meta-script that creates/updates the PKGBUILD for him. This make sense as I do the same thing for opera-next (opera development builds). So presumably he would add the logic to his meta script, not the PKGBUILD itself.

Det commented on 2012-01-09 08:41 (UTC)

1) And that couldn't all fit in one post? 2) Also that's gonna look so great in the Sources section there.

ruario commented on 2012-01-09 08:06 (UTC)

@t3ddy: I suspect this is what you want your meta script to do: echo http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_$(curl -s https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-i386/Packages.gz | zcat | awk -F "[ -]" '/Package: google-chrome-stable/ { getline ; print $2"-"$3 }')_$(uname -m | sed 's/i.86/i386/;s/x86_64/amd64/').deb It will print back whatever is the link to the current stable version.

ksmanis commented on 2012-01-07 01:11 (UTC)

PLEASE add kdebase-kdialog as an optdepend! Took me ages to figure out which package was needed.

<deleted-account> commented on 2012-01-03 16:06 (UTC)

Important for all KDE-Users: Chrome uses from version 16 on the default KDE-dialogues. Therefore the packages kdebase-kdialog has to be installed. Otherwise Chrome won't show any dialog-box under KDE.

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.

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