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

Scimmia commented on 2014-01-14 17:44 (UTC)

The real problem is that you didn't bump the pkgrel when you fixed the package in the first place. If the final binary package changes, you're supposed to bump the pkgrel. You failed.

big_bum commented on 2014-01-14 17:06 (UTC)

It will really be easier for all of us to simply increase the pgkrel. You are not rebuilding anything, you just have to edit one file...

Det commented on 2014-01-14 16:58 (UTC)

Unfortunately there's no such pkgrel that only affects those who have a "broken" system. When something that breaks things moves from [testing] to [core]/[extra] I'm against every single step of raising the pkgrel on any package that's not small as hell. It would have to be something seriously major and AUR rarely counts as such. That's life, that's Arch. If you don't have those libraries yet, then rebuild it or manually put them there. Those who do don't care.

Scimmia commented on 2014-01-14 16:39 (UTC)

nagging? It's required to rebuild it with the new libgcrypt, not nagging to help keep a working system.

Det commented on 2014-01-14 16:06 (UTC)

Not really. I did that change a long time ago and don't care about nagging anybody to rebuild it.

ushi commented on 2014-01-14 12:44 (UTC)

you could increase the pkgrel number. this is exactly the use case.

Det commented on 2014-01-13 21:37 (UTC)

Roughly, no, because for one, I would not bump the _version_ number to do that (which is '31.0.1650.63'), it would be the _release_ number (that is, '1') and two, the new libgcrypt 1.6.0-1 is the reason Google Chrome/Chromium/SRWare Iron do not work without the previous libraries being put in place (which is what I'm currently doing for you). Chrome is a binary package. I can't just go forward with my ambitious plans to rebuild it for a newer library that has been pulled in on another distribution, totally different fromt the ones they support. To sum up: - Chrome is built for libgcrypt 1.5.x - We use libgcrypt 1.6.x - They do NOT work together - Only Google can fix this - We (I) use the 1.5.x libraries in these packages to make Chrome working again - Big smile

RubenKelevra commented on 2014-01-13 21:25 (UTC)

could you please just increase the version-number while adding a depency to the new version libgcrypt-1.6.0-1? That would fix it for everybody. :)

franziskus commented on 2014-01-13 21:03 (UTC)

@jz_train just reinstall the package, also gets you libgcrypt.so.11. for a proper fix you have to wait for chromium/google to fix this

Det commented on 2014-01-13 20:16 (UTC)

And it's not out-of-date because of it..

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