Package Details: google-chrome-beta 132.0.6834.15-1

Git Clone URL: https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy)
Package Base: google-chrome-beta
Description: The popular web browser by Google (Beta Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 357
Popularity: 1.00
First Submitted: 2009-12-08 19:09 (UTC)
Last Updated: 2024-11-20 23:40 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

Pinned Comments

gromit commented on 2023-11-30 17:09 (UTC)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome beta version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-beta" | \
     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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 27 Next › Last »

Det commented on 2015-09-17 17:09 (UTC)

That's always the reason.

j3zz4h commented on 2015-09-02 21:41 (UTC)

The reason the checksum fails is because there is a new beta release. (line 8) --pkgver=45.0.2454.78 ++pkgver=46.0.2490.13 (line 29) --md5sums_i686=('86f89b18f0a4cff0243d5ba21e76ff17') ++md5sums_i686=('2bbaa53750bd6174af9e9a3fc6ace238') (line 30) --md5sums_x86_64=('3c9119aa02d2f550e29cfb959b116690') ++md5sums_x86_64=('37f75ae7b618a6cf1f48d20e8e1ddde1')

Det commented on 2015-08-27 12:02 (UTC)

Yeah it does. There's a new one up. Check the link, it's static.

dflt commented on 2015-08-27 10:06 (UTC)

# Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Beta%20updates # or use: $ curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }' @Det this really doesn't say why the checksum fails :)

Det commented on 2015-08-27 09:24 (UTC)

No, read the top of the PKGBUILD.

greyltc commented on 2015-08-27 08:58 (UTC)

Is the checksum correct? I'm getting: ==> Validating source files with md5sums... google-chrome-beta_45.0.2454.46_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!

Det commented on 2015-08-26 17:49 (UTC)

Flags are now read directly from ~/.config/chrome-beta-flags.conf, while $CHROMIUM_USER_FLAGS is unsupported. Didn't bump the pkgrel.

accountkiller commented on 2015-06-04 00:31 (UTC)

44.0.2403.30 beta

Det commented on 2015-05-14 05:17 (UTC)

Omg. Just flag it.

stratus_ss commented on 2015-05-13 23:40 (UTC)

md5sum google-chrome-beta_current_amd64.deb c67dd52b00d51ff7f59c0d8ac558924d google-chrome-beta_current_amd64.deb

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 27 Next › Last »