I fixed the error I reported above by changing that gzip line in the PKGBUILD to .../google-chrome-beta.1.
Search Criteria
Package Details: google-chrome-beta 132.0.6834.57-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-beta |
Description: | The popular web browser by Google (Beta Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 357 |
Popularity: | 0.60 |
First Submitted: | 2009-12-08 19:09 (UTC) |
Last Updated: | 2024-12-20 02:44 (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
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (42)
- 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)
- chromedriver-beta (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)
- Show 22 more...
Sources (3)
bulletmark commented on 2014-04-10 22:03 (UTC)
Det commented on 2014-04-10 21:52 (UTC)
Fixed.
bulletmark commented on 2014-04-10 21:49 (UTC)
This package updated today to 35.0.1916.27-1 but I am getting the following build error:
==> Starting package()...
-> Extracting the data.tar.lzma
-> Moving stuff in place
gzip: /tmp/yaourt-tmp-mark/aur-google-chrome-beta/pkg/google-chrome-beta/usr/share/man/man1/google-chrome.1: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
peterhu commented on 2014-03-19 19:55 (UTC)
For 34.0.1847.60-1 (x86-64), I'm getting a md5 mismatch: expecting 08c18ce9c91ebb3ced9978b0dca39239 but have 5a312386563cd41691671d530cac6c06.
bulletmark commented on 2014-03-08 02:24 (UTC)
Version 34.0.1847.45 locks up for me. I think it affects everybody with intel GPU as per https://code.google.com/p/chromium/issues/detail?id=345595.
wisecrick commented on 2014-03-06 08:14 (UTC)
Even worse, the browser itself usually hangs. I have to switch to google-chrome stable. It works very well.
kalpik commented on 2014-03-06 01:53 (UTC)
I have issues with flash too. Both Adobe flash and pepper flash. Browser hangs for a while, disk starts thrashing. Anyone knows why? Happens on dev too. Haven't tried stable yet.
wisecrick commented on 2014-03-05 03:10 (UTC)
Flash doesn't work at all! It always hangs!
<deleted-account> commented on 2014-02-28 16:01 (UTC)
I guess I can't :)
Pinned Comments
gromit commented on 2023-11-30 17:09 (UTC)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome beta version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.