From: mwyvr <mwyvr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] google-chrome: update to 132.0.6834.159.
Date: Mon, 03 Feb 2025 00:59:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54194@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
There is a new pull request by mwyvr against master on the void-packages repository
https://github.com/mwyvr/void-packages google-chrome-bump-132.0.6834.159
https://github.com/void-linux/void-packages/pull/54194
google-chrome: update to 132.0.6834.159.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
Latest Google Chrome release per the Chrome blog on January 28:
https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_28.html
A patch file from https://github.com/void-linux/void-packages/pull/54194.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-google-chrome-bump-132.0.6834.159-54194.patch --]
[-- Type: text/x-diff, Size: 1195 bytes --]
From 236b4a92081e007641bfe751a5c455268c6b7eb5 Mon Sep 17 00:00:00 2001
From: Mike Watkins <git@mikewatkins.ca>
Date: Sun, 2 Feb 2025 15:56:47 -0800
Subject: [PATCH] google-chrome: update to 132.0.6834.159.
---
srcpkgs/google-chrome/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/google-chrome/template b/srcpkgs/google-chrome/template
index 334213f41fc31c..130e14a3a32472 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,6 +1,6 @@
# Template file for 'google-chrome'
pkgname=google-chrome
-version=131.0.6778.204
+version=132.0.6834.159
revision=1
_channel=stable
archs="x86_64"
@@ -11,7 +11,7 @@ maintainer="Michael Aldridge <maldridge@voidlinux.org>"
license="custom:chrome"
homepage="https://www.google.com/chrome/"
distfiles="https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-${_channel}_${version}-1_amd64.deb"
-checksum=bc065416e7d17ef911b1b5e7a960f8cc4de181359b845a8395ab9737b9ba988c
+checksum=e54ef927fd5194e1feb705f05269405b81f47a5e2d9a001c7bc8df05fea0331c
skiprdeps="/opt/google/chrome/libqt5_shim.so /opt/google/chrome/libqt6_shim.so"
repository=nonfree
next reply other threads:[~2025-02-02 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 23:59 mwyvr [this message]
2025-02-03 2:53 ` [PR PATCH] [Merged]: " classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54194@inbox.vuxu.org \
--to=mwyvr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).