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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 91 Next › Last »

hagabaka commented on 2015-01-11 21:08 (UTC)

The subsititution to provide support for CHROMIUM_USER_FLAGS isn't right. It currently results in --user-data-dir="$CHROME_USER_DATA_DIR""$CHROMIUM_USER_FLAGS" "$@" So the value of CHROMIUM_USER_FLAGS is appended to the user data dir making Chrome use a new profile. The sed line in PKGBUILD should be modified to have a space before "$CHROMIUM_USER_FLAGS": sed -i 's/ "$@"/ "$CHROMIUM_USER_FLAGS" "$@"/' "$pkgdir"/opt/google/chrome-$_channel/google-chrome-$_channel Also, what about using CHROME_USER_FLAGS instead? Some flags, like --ppapi-flash-path= and --ppapi-flash-version=, aren't necessary for Chrome.

Det commented on 2015-01-09 13:13 (UTC)

That was actually something only the RPMs were missing. I'll think about it. Thanks.

ruario commented on 2015-01-09 13:09 (UTC)

The dependencies of Chrome unstable have recently changed. $ wget -q https://dl.google.com/linux/chrome/rpm/stable/x86_64/google-chrome-unstable-41.0.2267.0-1.x86_64.rpm $ mkdir google-chrome-unstable-41.0.2267.0-x86_64 $ tail -c+40093 google-chrome-unstable-41.0.2267.0-1.x86_64.rpm | xz -d | (cd google-chrome-unstable-41.0.2267.0-x86_64; cpio --quiet -imd) $ find google-chrome-unstable-41.0.2267.0-x86_64 -type f -exec file {} \; | grep 'LSB \(shared object\|executable\)' | cut -d: -f1 | xargs -n1 objdump -p | grep NEEDED | sort -u NEEDED ld-linux-x86-64.so.2 NEEDED libasound.so.2 NEEDED libcairo.so.2 NEEDED libc.so.6 NEEDED libcups.so.2 NEEDED libdbus-1.so.3 NEEDED libdl.so.2 NEEDED libexpat.so.1 NEEDED libfontconfig.so.1 NEEDED libfreetype.so.6 NEEDED libgcc_s.so.1 NEEDED libgconf-2.so.4 NEEDED libgdk_pixbuf-2.0.so.0 NEEDED libgdk-x11-2.0.so.0 NEEDED libgio-2.0.so.0 NEEDED libglib-2.0.so.0 NEEDED libgobject-2.0.so.0 NEEDED libgtk-x11-2.0.so.0 NEEDED libm.so.6 NEEDED libnspr4.so NEEDED libnss3.so NEEDED libnssutil3.so NEEDED libpango-1.0.so.0 NEEDED libpangocairo-1.0.so.0 NEEDED libplc4.so NEEDED libpthread.so.0 NEEDED librt.so.1 NEEDED libsmime3.so NEEDED libstdc++.so.6 NEEDED libwidevinecdm.so NEEDED libX11.so.6 NEEDED libXcomposite.so.1 NEEDED libXcursor.so.1 NEEDED libXdamage.so.1 NEEDED libXext.so.6 NEEDED libXfixes.so.3 NEEDED libXi.so.6 NEEDED libXrandr.so.2 NEEDED libXrender.so.1 NEEDED libXss.so.1 NEEDED libXtst.so.6 As you can see it no longer depends on libudev.so.0, so you can update the PKGBUILD to remove the "Symlinking missing Udev lib" section. P.S. Just a small "suggestion" (feel free to ignore). You may also note that the rpms now use xz compression and hence are of comparable size to the .deb packages. $ wget -q https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-unstable/google-chrome-unstable_41.0.2267.0-1_amd64.deb $ ls -l google-chrome-unstable-41.0.2267.0-1.x86_64.rpm google-chrome-unstable_41.0.2267.0-1_amd64.deb -rw-rw-r-- 1 ruario ruario 46762094 jan. 6 20:54 google-chrome-unstable_41.0.2267.0-1_amd64.deb -rw-rw-r-- 1 ruario ruario 47524020 jan. 6 20:54 google-chrome-unstable-41.0.2267.0-1.x86_64.rpm I mention this in case you want to reconsider using an .rpm as a source, rather than the .deb. As you know .rpms are auto-extracted by makepkg, thus allowing for a minor simplification to PKGBUILD.

Det commented on 2015-01-08 13:29 (UTC)

Old builds: http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-unstable/

Kwpolska commented on 2015-01-08 13:26 (UTC)

Newest version crashes on startup.

Det commented on 2014-12-10 12:00 (UTC)

It's been a little clunky since the update, but seemed to get fixed pretty fast.

spaceback commented on 2014-12-10 07:13 (UTC)

Hi, just for the record - amd64 .deb package is not available for download (404) as of now...

Det commented on 2014-12-09 22:36 (UTC)

Gomenasai. A fix has been committed in my official google-chrome-dev 41.0.2243.0-1 package.

dfryer1193 commented on 2014-12-09 22:33 (UTC)

I keep getting a failure in package() when trying to extract data.tar.lzma. Upon further investigation, it looks like data.tar.lzma in src/ has been renamed to data.tar.xz. Renaming data.tar.xz to data.tar.lzma, or changing data.tar.lzma to data.tar.xz in the PKGBUILD seems to fix this.

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 91 Next › Last »