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 .. 109 110 111 112 113 114 115 116 117 118 119 .. 157 Next › Last »

Det commented on 2014-01-16 07:00 (UTC)

I love you guys always handing out these patches to change a couple of lines :).

justinkb commented on 2014-01-15 23:36 (UTC)

http://bpaste.net/show/168513/ Simple patch to use the libgcrypt15 as suggested below

r2b2 commented on 2014-01-15 20:16 (UTC)

Now that there is a libgcrypt15 package in AUR for providing the old libgcrypt libraries, would it make sense to provide a dependency back to that? (Or at least reinstate the commented if statement which checks for libgcrypt and check for libgcrypt15 before copying the included libgcrypt libraries?)

l3u commented on 2014-01-15 08:19 (UTC)

Thanks for the update Det, and thanks for the work you're doing on it. I see a some people dissatisfied with the free service you're providing to the community on your own time. Let me say I am delighted to have an up to date system thanks to dedicated people like you. Deps change. Glitches happen. This is Arch. We have to live with this. If edges are too rough, there are other OSes out there. At least Arch let's you get the original PKGBUILD & friends and fix the problem by yourself, which is what I do when things go wrong, instead of pointing fingers. Life is hard for package maintainers. Behaving is the minimum we owe them.

Det commented on 2014-01-15 00:22 (UTC)

Please say this again; I loved this: > Comment by Scimmia 2014-01-14 17:44 > You failed. Bear with me here, darling. I didn't think this through. This wasn't the sort of running issue as you get with source packages where you first require a rebuild for [testing] users and then, a few weeks later, for everybody else. Chrome is a binary package. It _can't_ be rebuilt. I'm putting the actual library in, not recompiling for it. This could've _indeed_ (or rather should've) been done those 3 weeks ago, so now that non-testing users are also getting the update they'd already have a working Chrome. Well, apologies. Sometimes I think of some common solution straight away that doesn't actually apply to the current case at all. I'll try to be better?

lrm commented on 2014-01-14 20:51 (UTC)

The deb fails validation on 64-bit build. New checksum is: 5eda4b45f5482e526252a819ed5e78a3

w1ntermute commented on 2014-01-14 20:13 (UTC)

I agree with the other commenters, you really should have incremented pkgrel. That's the reason why pkgrel exists, like Scimmia said. OK, you made a mistake at first, but there's no reason to keep digging a deeper hole for yourself - just admit that you made a mistake and don't let it happen again.

« First ‹ Previous 1 .. 109 110 111 112 113 114 115 116 117 118 119 .. 157 Next › Last »