Package Details: google-chrome-dev 132.0.6793.2-1

Git Clone URL: https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy)
Package Base: google-chrome-dev
Description: The popular web browser by Google (Dev Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 653
Popularity: 1.32
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-10-24 21:01 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

Pinned Comments

gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (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 "Dev 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-unstable" | \
     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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 91 Next › Last »

Det commented on 2015-08-29 12:58 (UTC)

Flag. It. Don't. Post. The. Makepkg. Output.

EgidioCaprino commented on 2015-08-29 09:49 (UTC)

==> ERROR: One or more files did not pass the validity check!

Det commented on 2015-08-28 14:50 (UTC)

Read the top of the PKGBUILD.

GreenRaccoon23 commented on 2015-08-28 14:34 (UTC)

I think the md5sums for the 64 bit deb file should be this. I downloaded it twice and got the same result both times: 077c5822311c81f5404efa9c178e1c84

anish commented on 2015-08-27 18:10 (UTC)

Saweet ! Sorry for a delayed response, I had notifications turned off and did not realize

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

Wouldn't have had time to do this tomorrow with our gig of 8AM - 9PM, but there's now support for flags read directly from ~/.config/chrome-dev-flags.conf. Didn't bump the pkgrel, but already seemed to work. We apparently had manual support for $CHROMIUM_USER_FLAGS before through package().

Det commented on 2015-08-24 18:35 (UTC)

What I can do is add a ~/.config/chrome-flags.conf like Chromium has. Might also do well to have a separate one for all channels.

Det commented on 2015-08-22 14:25 (UTC)

I don't fancy that, no.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 91 Next › Last »