@grayich:
This is related to your configuration in /etc/yaourtrc (or maybe in /etc/makepkg.conf), where you set to store built packages in /var/cache/pacman/pkg/
Set another folder where you can store without needing root permissions, or always provide password.
Anyway, this issue is not related to this package, so further issues, ask for help in Arch Linux forums.
Search Criteria
Package Details: google-chrome 129.0.6668.58-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: | 2237 |
Popularity: | 8.05 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-09-17 21:41 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libcups (libcups-gssapiAUR, libcups-gitAUR, cups-gitAUR)
- 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 (41)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-bypass-paywalls (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)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 90 91 92 93 94 95 96 97 98 99 100 .. 157 Next › Last »
rafaelff commented on 2014-12-10 15:18 (UTC)
Det commented on 2014-12-10 11:50 (UTC)
Nothing at all to do with this package.
Det commented on 2014-12-09 19:34 (UTC)
The servers still offer .71 for Linux: http://googlechromereleases.blogspot.com/2014/12/stable-channel-update.html
Det commented on 2014-11-28 17:45 (UTC)
Yes, it works on a fresh install.
About the wrong source, you're probably using a poor AUR tool, or the system really is 64-bit:
$ uname -m
$ grep CARCH /etc/makepkg.conf
Av4t4r commented on 2014-11-28 17:40 (UTC)
I just did a fresh install with no permission issues. However, I did it on a 32bit system and I had to edit the PKGBUILD because it would otherwise only fetch the 64 bit package.
I edited _arch=i386 and updated the MD5 to
md5sums=('cc7c7cfcbd9982307b25989814739486'
'b7e752f549b215ac77f284b6486794b6')
Thanks for the package tho, hopefully this will get fixed soon.
Det commented on 2014-11-27 13:33 (UTC)
No, that's not the issue at all, aren't you getting the permission message after the upgrade? E.g.:
[...]
(1/1) upgrading google-chrome [#####################] 100%
warning: directory permissions differ on /usr/share/doc/google-chrome-stable/
filesystem: 700 package: 755
It means the existing permissions can't be changed without a manual intervention or a reinstall (uninstall/install).
nullptr_t commented on 2014-11-27 13:01 (UTC)
I know, you are fixing the permissions of the doc directory in PKGBUILD with
msg2 "Fixing permissions of documentation folder"
chmod 755 "$pkgdir"/usr/share/doc/google-chrome-$_channel/
but as of 39.0.2171.71-1 the problem still remains the same:
# ll -d /usr/share/doc/google-chrome-stable/
drwx------ 2 root root 4.0K Nov 27 13:46 /usr/share/doc/google-chrome-stable/
Don't know, what's the problem with "google-chrome-$_channel/", but maybe "$_channel" or ${_channel} (like in the sources-line) would help to clarify it as substring
jazztickets commented on 2014-11-26 03:19 (UTC)
google-chrome-stable_39.0.2171.65_amd64.deb ... FAILED
ERROR: One or more files did not pass the validity check!
rafaelff commented on 2014-11-13 18:10 (UTC)
I'm getting http error 404 on downloading the sources tarball.
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.