From: baalajimaestro <baalajimaestro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] google-chrome: update to 115.0.5790.110.
Date: Wed, 26 Jul 2023 05:52:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45256@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
There is a new pull request by baalajimaestro against master on the void-packages repository
https://github.com/baalajimaestro/void-packages update/google-chrome/115.0.5790.110
https://github.com/void-linux/void-packages/pull/45256
google-chrome: update to 115.0.5790.110.
Testing the changes
I tested the changes in this PR: YES
Local build testing
I built this PR locally for my native architecture, glibc, x86_64
A patch file from https://github.com/void-linux/void-packages/pull/45256.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/google-chrome/115.0.5790.110-45256.patch --]
[-- Type: text/x-diff, Size: 1281 bytes --]
From 3b6f9dff4a9a2d4fe074ad0837e9831b6feab1b9 Mon Sep 17 00:00:00 2001
From: baalajimaestro <me@baalajimaestro.me>
Date: Wed, 26 Jul 2023 09:17:23 +0530
Subject: [PATCH] google-chrome: update to 115.0.5790.110.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
---
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 b5ff1ac9a9fa0..8c778d8b53489 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,6 +1,6 @@
# Template file for 'google-chrome'
pkgname=google-chrome
-version=115.0.5790.102
+version=115.0.5790.110
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=b4eece9302ae3afa5bca317a965e3012d3e242ef79556e0a42a635b617eec7a2
+checksum=234f953895107cb9285be2470ef4f6a16085cf9f35864b76df44a3d345a252f0
_license_checksum=8023b18fb5118ef65d586363e53909861bd1a9676e5eb83c20fd3ac6e33ea0be
skiprdeps="/opt/google/chrome/libqt5_shim.so"
next reply other threads:[~2023-07-26 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 3:52 baalajimaestro [this message]
2023-07-26 15:44 ` [PR PATCH] [Merged]: " sgn
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-45256@inbox.vuxu.org \
--to=baalajimaestro@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).