Thanks shock_one. The md5sum provided by shock_one is for the EULA. When you edit the build, replace the 2nd md5sum in parentheses with the one provided by shock_one and the build will work.
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.47 |
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 .. 31 32 33 34 35 36 37 38 39 40 41 .. 91 Next › Last »
colinkeenan commented on 2013-10-17 23:32 (UTC)
shock_one commented on 2013-10-17 15:10 (UTC)
New md5sum: a3a49767c80e92cca63b7a33aadfb2af
corruptmemory commented on 2013-10-17 14:38 (UTC)
Updated EULA breaking install:
==> Validating source files with md5sums...
google-chrome-unstable_32.0.1671.3_amd64.deb ... Passed
eula_text.html ... FAILED
Det commented on 2013-10-13 12:10 (UTC)
Rebuilding could've also sufficed.
Kwpolska commented on 2013-10-13 08:35 (UTC)
PS. setting the path to “/opt/google/chrome-unstable/google-chrome” fixed the problem for me.
Kwpolska commented on 2013-10-13 08:26 (UTC)
Since the last update (chrome 32), the launcher is broken. It uses an executable path that the KDE icon-only task manager does not like, which results in me being unable to have one nice icon for chrome.
Det commented on 2013-10-11 15:51 (UTC)
That didn't last too long. Fixed.
palmtree5 commented on 2013-10-09 19:00 (UTC)
I had to edit and remove the "-unstable" as misc said. After that, it worked fine
misc commented on 2013-10-09 18:25 (UTC)
Remove all nine "-unstable" from the build() for this version.
oconnors11 commented on 2013-10-09 15:05 (UTC)
I am getting this any ideas?
-> Extracting google-chrome-unstable_32.0.1664.3_amd64.deb with bsdtar
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting package()...
-> Extracting the data.tar.lzma
-> Moving stuff in place
mv: cannot stat ‘/var/build/google-chrome-dev/pkg/google-chrome-dev/opt/google/chrome-unstable/google-chrome-unstable.desktop’: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
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.