Package Details: google-chrome 131.0.6778.69-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: 2245
Popularity: 8.41
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-12 20:25 (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 »

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.

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

I was wondering today if it might be possible to get at the version number and checksum information direct from the google repo, and by trial and error I have found today that it is possible to get at this information. By typing the command as in the following you can see that the right information is extracted: [mike@home1 chrome-test]$ curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/primary.xml.gz |gzip -d| awk -F\" '/<name>google-chrome-stable<\/name><arch>/ { print $6 ; print $8 ; print $13}' 17.0.963.65 124586 >2d0a251fb70396a2943c85d58aa859e1392fd101</checksum><summary>Google Chrome</summary><description>The web browser from Google So in principle the "ver" and "rel" numbers are easy to extract and in addition the sha1sum can be extracted from the last line as well - and this could allow a single aur PGGBUILD file to be written that would extract all the required information without having to download a new tarball each time google updates chrome (unless they changed the format of the "primary.xml.gz file that contains the data. I wonder if a suitable PGKBUILD file could be constructed based on the above information? I am not that expert at awk commands and it might be quicker if someone really familiar with awk could do that? If so it would make for a really nice update to this AUR package, since the current file needs to be manually updated with the new version numbers and checksum every time google updates chrome? The checksum would need to be changed from md5 to sha1 but that is presumably not a huge change? A very similar scheme would presumably also work for beta and dev versions? Either way it is easy enough to download the "primary.xm.gz" file to tinker with the rest of the necessary scripting. I hope this might help? Thanks

<deleted-account> commented on 2012-03-05 14:20 (UTC)

fixed PKGBUILD (new version): http://pastebin.com/4jymgTbY

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