google-chrome-dev has updated 25.0.1323.1
download url:
http://dl.google.com/linux/chrome/rpm/stable/x86_64/google-chrome-unstable-25.0.1323.1-167142.x86_64.rpm
Search Criteria
Package Details: google-chrome-dev 133.0.6847.2-1
Package Actions
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.44 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2024-11-21 19:42 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet5 (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (40)
- bitwarden-chromium (requires google-chrome) (optional)
- captive-browser-git (requires google-chrome) (optional)
- chrome-extension-bitwarden-git (requires google-chrome) (optional)
- chrome-extension-ocrs-git (requires google-chrome)
- chromedriver (requires google-chrome) (optional)
- chromium-extension-adnauseam (requires google-chrome) (optional)
- chromium-extension-autoscroll (requires google-chrome) (optional)
- chromium-extension-plasma-integration (requires google-chrome) (optional)
- chromium-extension-runet-censorship-bypass (requires google-chrome) (optional)
- chromium-material-icons-for-github-bin (requires google-chrome) (optional)
- chromium-vencord (requires google-chrome) (optional)
- chromium-vencord-bin (requires google-chrome) (optional)
- chromium-vencord-git (requires google-chrome) (optional)
- dedao-dl-bin (requires google-chrome) (optional)
- endpoint-verification-chrome (requires google-chrome)
- endpoint-verification-minimal (requires google-chrome)
- ff2mpv-go-git (requires google-chrome) (optional)
- ff2mpv-rust (requires google-chrome) (optional)
- hub-kids (requires google-chrome) (optional)
- hub-young (requires google-chrome) (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 91 Next › Last »
wolftankk commented on 2012-11-13 06:52 (UTC)
ravicious commented on 2012-11-06 19:45 (UTC)
I get the same error as MajorTom:
curl: (22) The requested URL returned error: 404 Not Found
<deleted-account> commented on 2012-10-31 05:11 (UTC)
current version should be 24.0.1312.1-164922 judging by the wget stuff
wizetek commented on 2012-10-17 02:21 (UTC)
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading google-chrome-unstable-24.0.1290.1-160787.i386.rpm
dcelasun commented on 2012-10-15 16:18 (UTC)
For me, Chrome 24 broke GPU acceleration with Catalyst (worked fine with 23). "about:gpu" shows "GpuProcessHostUIShim: GPU Process Crashed." and the GL information is completely empty. Screenshot: http://i.imgur.com/DGLoT.png
ruario commented on 2012-08-27 07:58 (UTC)
@Ner0: Pulling the information from the header of the rpm package or by querying the YUM or APT databases is better than relying on pkgs.org to be up to date. After all Google are the ones updating the packages, so it is best to get the information directly from them rather than a third party.
Det commented on 2012-08-24 07:52 (UTC)
Wasn't just now.
Ner0 commented on 2012-08-15 13:25 (UTC)
You could also check http://pkgs.org/google-chrome-for-linux they're always up to date
ruario commented on 2012-08-15 09:53 (UTC)
@jdarnold: You can also work out the build version (including minor revision) numbers by reading it from the first 96 bytes of the of the rpm header, e.g.:
$ curl -sr0-96 http://dl.google.com/linux/direct/google-chrome-unstable_current_i386.rpm | strings
sjakub commented on 2012-08-15 07:57 (UTC)
22.0.1229.6-151414 is there
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.