Package Details: google-chrome 131.0.6778.69-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: 2244
Popularity: 7.52
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-12 20: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 .. 133 134 135 136 137 138 139 140 141 142 143 .. 157 Next › Last »

ruario commented on 2012-08-14 10:44 (UTC)

@Det: Ok, well as I said I am not personally adverse to using the deb again if t3ddy wants to save some bandwidth for users of this PKGBUILD. I honestly thought that Google would have LZMA or XZ rpms available by now and as you know I suggested the format of rpms as they are more consistent with Arch conventions, making for a potentially easier to maintain PKGBUILD. I was *trying* to help, not inconvenience people. ;) Anyway, I suspect the bigger plus for t3ddy in switching to rpm was a predictable way to gather the ${_verbld} information for the meta script he uses to update the PKGBUILD. The command I supplied him previously did this. However, given that I now see that you can also query the APT repository to gather this information (as outlined in my previous post) I guess that advantage is moot. P.S. I guess I am lucky that my internet connection is fast enough that even with a 23% increase I can still download the rpms within a couple of seconds.

Det commented on 2012-08-14 10:01 (UTC)

Actually more than slightly. The 64-bit .77 rpm is 42.2MB, while the deb is only 32.3MB. That's a -23% difference.

ruario commented on 2012-08-14 07:55 (UTC)

@tancrackers: No it isn't 'optimised' for Ubuntu. The package contents of the rpm and deb files are identical apart from a different updater cron job file and 3 extra Debian specific files in the deb. You can confirm this as follows: $ mkdir rpm deb $ wget -qO- https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm | bsdtar -xf- -C rpm $ wget -qO- https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb | bsdtar -xOf- data.tar.* | bsdtar -xf- -C deb $ diff -qr rpm deb Files rpm/etc/cron.daily/google-chrome and deb/etc/cron.daily/google-chrome differ Only in deb/usr/share: applications Only in deb/usr/share: doc Only in deb/usr/share: menu I would imagine that Google build the binaries only once per architecture and then package them into to different formats (this is also what happens with Opera). @Det: If t3ddy wants to use the debs as a source, it is fine by me. I suggested the rpms as source because because they simplify the packaging steps, i.e. they are auto-unpacked by makepkg, they are more generic (less distro specific stuff to remove) and because at the time I felt it was easier to automate gathering the version and revision (${_verbld}) information, allowing for source URLs that reflect the actual build being packaged. As it happens I since discovered you can gather this information by parsing the APT repository meta-data. As you state however the deb files are slightly smaller, though I was hopeful that by now Google would have fixed this. There is nothing stopping them using LZMA/XZ compressed rpms as they can be handled by all their supported rpm-based distros (currently only Fedora and openSUSE). Anyway, for those wishing to manually update the PKGBUILD, you can work out the latest version and revision (${_verbld}) information (to update the URL) by reading it out of the first 96 bytes of data in the header of the rpm, like so: $ wget -qO- https://dl.google.com/linux/direct/google-chrome-stable_current_i386.rpm | head -c96 | strings | rev | awk -F"[:-]" '/emorhc/ { print $1 "-" $2 }' | rev 21.0.1180.77-150576 Alternatively you can pull it out of the YUM repository meta-data: $ wget -qO- https://dl.google.com/linux/chrome/rpm/stable/i386/repodata/other.xml.gz | gzip -d | awk -F\" '/-stable/ { print $10 "-" $12 }' 21.0.1180.77-150576 Or if you are using the .deb as a source from the APT repository meta-data: $ wget -qO- https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-i386/Packages.gz | gzip -d | awk '/Package: google-chrome-stable/ { getline ; print $2 }' 21.0.1180.77-r150576 The format of the version specific URLs is as follows: https://dl.google.com/linux/chrome/rpm/stable/${_arch}/google-chrome-${_channel}-${_verbld}.${_arch}.rpm or https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-${_channel}/google-chrome-${_channel}_${_verbld}_${_arch}.deb

mike.cloaked commented on 2012-08-13 21:02 (UTC)

Seems that version 21.0.1180.77 was pushed out rather soon after the previous version!

Det commented on 2012-08-12 10:37 (UTC)

Naturally. Deb: http://pastebin.com/cP2rZPwm Rpm: http://pastebin.com/6329UEjW

antihero commented on 2012-08-12 09:57 (UTC)

Det do you have an up-to-date PKGBUILD I could use?

Det commented on 2012-08-12 09:55 (UTC)

Because the guy I had this discussion with felt .rpm's were more fit for Arch due to its lack of debianisms (the .menu and changelog.gz) even after it was revealed they use an inferior compression algorithm (Bzip2 vs LZMA). E: We originally used debs. I still do with my local package.