The final vote. “What should be the pkgdesc of AUR/google-chrome?” With 82 votes:
● "One fast, simple, and secure browser for all your devices (Stable Channel)" - 17 votes (21%)
● "The popular and trusted web browser by Google (Stable Channel)" - 65 votes (79%)
Now, my deciding vote of 49 votes will be cast and the winner is...
..no, I’m kidding, I’m kidding. Pkgdesc changed. ^^
Search Criteria
Package Details: google-chrome 131.0.6778.85-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome |
Description: | The popular web browser by Google (Stable Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 2248 |
Popularity: | 10.09 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-19 19:19 (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 (40)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-extension-adnauseam (optional)
- chromium-extension-autoscroll (optional)
- chromium-extension-plasma-integration (optional)
- chromium-extension-runet-censorship-bypass (optional)
- chromium-material-icons-for-github-bin (optional)
- chromium-vencord (optional)
- chromium-vencord-bin (optional)
- chromium-vencord-git (optional)
- dedao-dl-bin (optional)
- endpoint-verification-chrome
- endpoint-verification-minimal
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- hub-kids (optional)
- hub-young (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 52 53 54 55 56 57 58 59 60 61 62 .. 157 Next › Last »
Det commented on 2017-10-01 00:35 (UTC) (edited on 2017-10-01 00:42 (UTC) by Det)
zman0900 commented on 2017-09-28 01:31 (UTC)
@ratan: `rm ~/.cache/pacaur/google-chrome/eula_text.html` should fix it.
ratan commented on 2017-09-27 19:30 (UTC)
getting the following when building from pacaur:
:: google-chrome package(s) failed to install.
:: ensure package version does not mismatch between .SRCINFO and PKGBUILD
:: ensure package name has a VCS suffix if this is a devel package
Det commented on 2017-09-27 02:40 (UTC)
libc++'s not required by google-chrome?
fuan_k commented on 2017-09-26 23:57 (UTC)
If you get the following errors (while building libc++)
==> Verifying source file signatures with gpg...
llvm-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
libcxx-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
libcxxabi-5.0.0.src.tar.xz ... FAILED (unknown public key 0FC3042E345AD05D)
==> ERROR: One or more PGP signatures could not be verified!
It seems that a way to fix it is to run the following command (ref: https://aur.archlinux.org/pkgbase/libc%2B%2B/)
gpg --recv-keys B6C8F98282B944E3B0D5C2530FC3042E345AD05D
Det commented on 2017-09-26 08:32 (UTC) (edited on 2017-09-26 08:42 (UTC) by Det)
Actually, about that, those who might find it interesting or entertaining: https://wiki.archlinux.org/index.php/User_talk:Vesath#PKGBUILD#Integrity
Det commented on 2017-09-25 09:48 (UTC) (edited on 2017-09-26 15:12 (UTC) by Det)
That's a misconception between preimage resistance and collision resistance: https://www.wikiwand.com/en/MD5#/Preimage_vulnerability
Collision basically means finding/generating any 2 strings/files that have the same hash. For MD5 since 2013 that seems to be 2^18, which "runs in less than a second on a regular computer".
Preimage is having that one predetermined file, for which you need to find/generate a string/file to match. Since 2009 that sems to be 2^123.4, which is... quite a lot more.
E: What am I doing. I linked the same page you did. Sublinked.
JelteF commented on 2017-09-25 09:15 (UTC)
Could the checksums in this package please be changed to sha256 instead of md5? MD5 hasn't been a secure hash function since a long time now: https://en.wikipedia.org/wiki/MD5#Security
Det commented on 2017-09-25 05:26 (UTC)
> Your package google-chrome [1] has been flagged out-of-date by ytarch [2]:
>
> because md5sum is invalid. I can't build package.
lol
Det commented on 2017-09-24 17:51 (UTC) (edited on 2017-09-24 17:51 (UTC) by Det)
> Your package google-chrome [1] has been flagged out-of-date by ytarch [2]:
>
> invalid md5sum.
No it isn't..
Clear your cache.
Pinned Comments
gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (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 "Stable 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.