Package Details: google-chrome-dev 83.0.4100.3-1

Git Clone URL: (read-only, click to copy)
Package Base: google-chrome-dev
Description: The popular and trusted web browser by Google (Dev Channel)
Upstream URL:
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: luzifer
Last Packager: luzifer
Votes: 635
Popularity: 0.62
First Submitted: 2009-06-05 21:02
Last Updated: 2020-04-01 19:53

Dependencies (13)

Required by (37)

Sources (3)

Pinned Comments

Det commented on 2016-03-09 05:02

✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in:, or use:

$ curl -sL | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL | sed -n '54p'

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

sanerb commented on 2018-01-22 09:46

hey det, would it help you avoid unnecessary comments if i write a python script for you that you can cron that'll fetch and parse that .xml.gz and email you if it updates?

Det commented on 2018-01-09 20:07

Your package google-chrome-dev [1] has been flagged out-of-date by gehzumteufel [2]:

I cannot explain why, but the md5sum does not match. Whether via downloading the file directly, or via pacaur. The sum I get is ae421158a6e7268c313150b8fff6c2a0. Which does not match any of the sums in the pkgbuild.

Because there is a new version, as per the instructions in the pinned comment.

Det commented on 2018-01-04 23:20

staticfloat flagged google-chrome-dev out-of-date on 2018-01-04 for the following reason:

md5 checksums out of date

No it isn't.

denixx commented on 2017-11-29 13:34

@dsifford Thanks for suggestion, though. :)

denixx commented on 2017-11-29 13:31

Line 47 of PKGBUILD:
install -Dm644 "$pkgdir"/opt/google/chrome-$_channel/product_logo_${i/x*}-${pkgname/*-}.png \

between ${i/x*}-${pkgname/*-}
change minus to underscore:

like this:
install -Dm644 "$pkgdir"/opt/google/chrome-$_channel/product_logo_${i/x*}_${pkgname/*-}.png \

dsifford commented on 2017-11-29 01:32

Error in latest build:

install: cannot stat '/home/dsifford/.cache/pacaur/google-chrome-dev/pkg/google-chrome-dev/opt/google/chrome-unstable/product_logo_16.png': No such file or directory

Looking in the directory specified above, it looks like chrome is now appending "_dev" after the number.. So, in the above case, it would be "product_logo_16_dev.png" rather than "product_logo_16.png"...

Looks like that should be a quick fix here:

Det commented on 2017-11-03 20:06

> lytedev flagged google-chrome-dev out-of-date on 2017-11-02 for the following reason:
> Failing checksum; flagging as requested.

Matches just fine for me.

Det commented on 2017-10-13 18:59


potatoe commented on 2017-10-13 17:18

google-chrome-unstable_63.0.3236.7_amd64.deb seems to ship the man page as a .gz, causing the PKGBUILD to fail when trying to gzip a no longer present uncompressed man page:

gzip: ...../pkg/google-chrome-dev/usr/share/man/man1/google-chrome-unstable.1: No such file or directory

$ ls pkg/google-chrome-dev/usr/share/man/man1/

Commenting out the gzip command in the PKGBUILD allows it to build.

Det commented on 2017-10-03 18:23

It's often good idea to try pure makepkg first. This one's a Pacaur bug:

Workaround: $ rm ~/.cache/pacaur/google-chrome-dev/eula_text.html