Package Details: google-chrome-dev 126.0.6452.3-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: 651
Popularity: 0.97
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-05-03 19:34 (UTC)

Dependencies (12)

Required by (36)

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 2 3 4 5 6 7 8 9 10 .. 91 Next › Last »

Det commented on 2018-01-09 20:07 (UTC)

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 (UTC)

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 (UTC)

@dsifford Thanks for suggestion, though. :)

denixx commented on 2017-11-29 13:31 (UTC)

@dsifford 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: ${i/x*}_${pkgname/*-} like this: install -Dm644 "$pkgdir"/opt/google/chrome-$_channel/product_logo_${i/x*}_${pkgname/*-}.png \

dsifford commented on 2017-11-29 01:32 (UTC)

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: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome-dev#n47

Det commented on 2017-11-03 20:06 (UTC)

> 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 (UTC)

'xed.

potatoe commented on 2017-10-13 17:18 (UTC)

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/ google-chrome-unstable.1.gz Commenting out the gzip command in the PKGBUILD allows it to build.

Det commented on 2017-10-03 18:23 (UTC) (edited on 2017-10-13 19:00 (UTC) by Det)

It's often good idea to try pure makepkg first. This one's a Pacaur bug: https://github.com/rmarquis/pacaur/issues/758 Workaround: $ rm ~/.cache/pacaur/google-chrome-dev/eula_text.html

bakgwailo commented on 2017-10-03 18:20 (UTC)

Getting the following error when trying to update: :: Installing google-chrome-dev package(s)... :: google-chrome-dev 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

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