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 .. 52 53 54 55 56 57 58 59 60 61 62 .. 157 Next › Last »

ratan commented on 2017-09-27 19:30 (UTC)

getting the following when building from pacaur: :: google-chrome package(s) failed to install. :: ensure package version does not mismatch between .SRCINFO and PKGBUILD :: ensure package name has a VCS suffix if this is a devel package

Det commented on 2017-09-27 02:40 (UTC)

libc++'s not required by google-chrome?

fuan_k commented on 2017-09-26 23:57 (UTC)

If you get the following errors (while building libc++) ==> Verifying source file signatures with gpg... llvm-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D) libcxx-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D) libcxxabi-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D) ==> ERROR: One or more PGP signatures could not be verified! It seems that a way to fix it is to run the following command (ref: https://aur.archlinux.org/pkgbase/libc%2B%2B/) gpg --recv-keys B6C8F98282B944E3B0D5C2530FC3042E345AD05D

Det commented on 2017-09-26 08:32 (UTC) (edited on 2017-09-26 08:42 (UTC) by Det)

Actually, about that, those who might find it interesting or entertaining: https://wiki.archlinux.org/index.php/User_talk:Vesath#PKGBUILD#Integrity

Det commented on 2017-09-25 09:48 (UTC) (edited on 2017-09-26 15:12 (UTC) by Det)

That's a misconception between preimage resistance and collision resistance: https://www.wikiwand.com/en/MD5#/Preimage_vulnerability Collision basically means finding/generating any 2 strings/files that have the same hash. For MD5 since 2013 that seems to be 2^18, which "runs in less than a second on a regular computer". Preimage is having that one predetermined file, for which you need to find/generate a string/file to match. Since 2009 that sems to be 2^123.4, which is... quite a lot more. E: What am I doing. I linked the same page you did. Sublinked.

JelteF commented on 2017-09-25 09:15 (UTC)

Could the checksums in this package please be changed to sha256 instead of md5? MD5 hasn't been a secure hash function since a long time now: https://en.wikipedia.org/wiki/MD5#Security

Det commented on 2017-09-25 05:26 (UTC)

> Your package google-chrome [1] has been flagged out-of-date by ytarch [2]: > > because md5sum is invalid. I can't build package. lol

Det commented on 2017-09-24 17:51 (UTC) (edited on 2017-09-24 17:51 (UTC) by Det)

> Your package google-chrome [1] has been flagged out-of-date by ytarch [2]: > > invalid md5sum. No it isn't.. Clear your cache.

Det commented on 2017-09-23 17:45 (UTC) (edited on 2017-09-23 17:45 (UTC) by Det)

> Your package google-chrome [1] has been flagged out-of-date by lookcrabs [2]: > > ensure package version does not mismatch between .SRCINFO and PKGBUILD Read damn comments.

« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 157 Next › Last »