Package Details: google-chrome-dev 133.0.6847.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: 654
Popularity: 1.35
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-11-21 19:42 (UTC)

Dependencies (12)

Required by (40)

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 .. 36 37 38 39 40 41 42 43 44 45 46 .. 91 Next › Last »

<deleted-account> commented on 2013-07-17 11:55 (UTC)

I'm using Yaourt to get the package, and can't install it due to the signature thing, is there an arg to filter that on Yaourt? if not, you might wanna get look into that. Also since this is a dev meta, can't you refer to the latest package without hardcoded version strings? Just guessing here probably I'm 100% wrong, just leaving it out there anyway. Thanks for the effort, tho :)

spsf64 commented on 2013-07-17 02:21 (UTC)

Ver 30.x is out!

codekoala commented on 2013-06-27 13:25 (UTC)

@Det: Touche :) I was just asking because it was added some road bumps in my normal workflow when maintaining my own repository of packages like this. Thanks for the clarification!

Det commented on 2013-06-26 19:57 (UTC)

1) Yes. 2) Well, using 'updpkgsums && makepkg -si' instead of 'makepkg -si --skipinteg' is only worthwhile if you're building multiple times in a row - which you wouldn't be with this. updpkgsums is meant as a replacement for 'makepkg -g >> PKGBUILD'. You don't need to use it, if you're not uploading anything.

codekoala commented on 2013-06-26 13:59 (UTC)

@Det I'm a bit confused by the PKGEXT change. What's the point in doing that? Simply to speed up build/install time by removing the compression step? Also, there's a new utility to update the hashes automatically: updpkgsums. Run that in the same directory as a PKGBUILD and it will make sure the sums are correct, so you shouldn't need to use --skipinteg.

Det commented on 2013-06-25 19:40 (UTC)

So I changed the source urls to .debs (up to 12M less download, cutting off roughly ~21%, along with faster extraction times), added the license and changed the compression to PKGEXT=".pkg.tar". The urls now also always point to the latest release, so in case I'm not there in time all you need to do is check the pkgver with either: 1) http://googlechromereleases.blogspot.com/search/label/Dev%20updates 2) curl -s https://dl.google.com/linux/direct/google-chrome-unstable_current_x86_64.rpm | head -c96 | strings 3) curl -s http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }' and then rebuild with '--skipinteg'.

t3ddy commented on 2013-06-25 18:00 (UTC)

Perfect!

Det commented on 2013-06-25 17:57 (UTC)

No, I got my own. Thanks.

t3ddy commented on 2013-06-25 17:57 (UTC)

Good, do you want the sripts I was using?

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 91 Next › Last »