Package Details: google-chrome 131.0.6778.85-1

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: 2247
Popularity: 9.55
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-19 19:19 (UTC)

Dependencies (12)

Sources (3)

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:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 142 143 144 145 146 147 148 149 150 151 152 .. 157 Next › Last »

Hexcles commented on 2012-03-07 00:18 (UTC)

Package out of date. File not found(404) on dl.google.com.

<deleted-account> commented on 2012-03-06 18:57 (UTC)

I am having problems because of the openssl-compatibility dependency. I am not able to install that package because of errors: error: failed to commit transaction (conflicting files) openssl-compatibility: /usr/lib/libcrypto.so.0.9.8 exists in filesystem openssl-compatibility: /usr/lib/libssl.so.0.9.8 exists in filesystem Errors occurred, no packages were upgraded.

mike.cloaked commented on 2012-03-05 22:43 (UTC)

OK I have just seen the other comments from early January now - I did not spot that there were additional comments not listed by default on this page unless specifically clicking on the appropriate link - apologies as I am fairly newly converted to arch from Fedora which I was using for the past 8 years! I note that there were similar suggestions but not exactly the same as mine early on in the discussion from a couple of months back - anyway if t3ddy can utilise the additional info from my earlier comment in his script then it may be of help to him in maintaining chrome updates. It does need a little scripting work but it should be do-able. The only change in the PKGBUILD file would then be a switch to sha1sum instead of md5sum but that is a minor change.

mike.cloaked commented on 2012-03-05 22:18 (UTC)

OK - no problem - if the t3ddy script that generates the pkgbuild file can use the information that I gave then it should be relatively simple to extract the version number and compare with the previous version and only generate a new packagebuild file if the version changes - that could even be automated and executed say daily? I was only trying to see if there was a way to both reduce the maintainer workload and also make the update perhaps more timely... I hope that is potentially useful?

Det commented on 2012-03-05 22:03 (UTC)

I meant that t3ddy mentioned some time ago to be using some script to generate the PKGBUILD for him. And the problem with auto-fetching PKGBUILD is that yes, it's better when the package would otherwise be out-of-date and it also eases up the maintainer's task but the whole point of _having_ a packaging system with linux is that the system/packages update automatically. With semi-automatically updating packages you'd first have to find out whether there even was a new version and then manually reinstall the package. Who wants that? E: also, I mistook you for ruario. That's why I figured you knew about the script thing.

mike.cloaked commented on 2012-03-05 21:43 (UTC)

If there is a way to utilise the downloaded file that I suggested, and extract the information required within the existing but amended PKGBUILD file then it would make life easier for the users? I don't know if it is possible but at least there is a chance to make the whole thing automatic rather than needing manual intervention by the maintainer each time chrome is updated? Of course I could just be too naive to know there is no simple way to make this work and would be happy to be informed whether or not my suggestion is possible or not.

mike.cloaked commented on 2012-03-05 20:40 (UTC)

Which script does t3ddy use? Why is it a better solution than having a self-contained script so that new amended copies are not necessary mostly? What is the problem with curl/awk anyway?

Det commented on 2012-03-05 18:43 (UTC)

If you're talking about replacing the "pkgver" line with some curl/awk odds and ends, you can forget it. If you're just talking about the script t3ddy is using, then that's a very nice solution.

« First ‹ Previous 1 .. 142 143 144 145 146 147 148 149 150 151 152 .. 157 Next › Last »