From: atk <atk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] google-chrome: update to 107.0.5304.110
Date: Wed, 09 Nov 2022 21:08:26 +0100 [thread overview]
Message-ID: <20221109200826.Zyucka8c5C5dgUONyf5lVWMqnvId93niS_O9GqEA2UY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40410@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
There is an updated pull request by atk against master on the void-packages repository
https://github.com/atk/void-packages google-chrome-107.0.5304.110
https://github.com/void-linux/void-packages/pull/40410
google-chrome: update to 107.0.5304.110
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/40410.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-google-chrome-107.0.5304.110-40410.patch --]
[-- Type: text/x-diff, Size: 1075 bytes --]
From 19605c1a89d2600d0a176cf318f9873dc395680d Mon Sep 17 00:00:00 2001
From: Alex Lohr <alexthkloss@web.de>
Date: Wed, 9 Nov 2022 13:45:32 +0100
Subject: [PATCH] google-chrome: update to 107.0.5304.110
---
srcpkgs/google-chrome/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/google-chrome/template b/srcpkgs/google-chrome/template
index 70d751f4f122..54988d2d7c9f 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,7 +1,7 @@
# Template file for 'google-chrome'
pkgname=google-chrome
-version=107.0.5304.87
-revision=2
+version=107.0.5304.110
+revision=1
_channel=stable
archs="x86_64"
hostmakedepends="tar xz python3 python3-html2text python3-setuptools"
@@ -21,7 +21,7 @@ _chromeUrl="${_baseUrl}/${_filename}"
_licenseUrl="https://www.google.com/intl/en/chrome/terms/"
distfiles="$_chromeUrl"
-checksum=422b1b0732ed0f69d4638858d55f83c65c3b87773b1f033130bdbad975c44699
+checksum=52e6d1be974c36cb40469f03b128cf21b36359a05fdadbb2e0379fbb17ef341b
do_extract() {
mkdir -p ${DESTDIR}
next prev parent reply other threads:[~2022-11-09 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:46 [PR PATCH] " atk
2022-11-09 20:08 ` atk [this message]
2022-11-09 20:45 ` [PR PATCH] [Merged]: " Duncaen
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=20221109200826.Zyucka8c5C5dgUONyf5lVWMqnvId93niS_O9GqEA2UY@z \
--to=atk@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).