From: mnabid <mnabid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] google-chrome: update to 87.0.4280.66
Date: Wed, 18 Nov 2020 01:08:53 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26469@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 326 bytes --]
There is a new pull request by mnabid against master on the void-packages repository
https://github.com/mnabid/void-packages google-chrome
https://github.com/void-linux/void-packages/pull/26469
google-chrome: update to 87.0.4280.66
A patch file from https://github.com/void-linux/void-packages/pull/26469.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-google-chrome-26469.patch --]
[-- Type: text/x-diff, Size: 968 bytes --]
From 7c0ee99d018c7d842e1196c4e8f7b7e98d2c4d2e Mon Sep 17 00:00:00 2001
From: Nafis <mnabid.25@outlook.com>
Date: Wed, 18 Nov 2020 06:05:10 +0600
Subject: [PATCH] google-chrome: update to 87.0.4280.66
---
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 51c5c857f17..2da4b0ec55c 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,5 +1,5 @@
# Template file for 'google-chrome'
-_chromeVersion=86.0.4240.198
+_chromeVersion=87.0.4280.66
_chromeRevision=1
_channel=stable
@@ -22,7 +22,7 @@ _chromeUrl="${_baseUrl}/${_filename}"
_licenseUrl="https://www.google.com/intl/en/chrome/terms/"
distfiles="$_chromeUrl"
-checksum=3d0055cf8db589d1bc6eb6504791d141e7008fb34cdb85bd1d194893c7d1d061
+checksum=e7e4c6a2108140c572562867f522d0311a25ce03ea36c5452cb8431865871226
do_extract() {
mkdir -p ${DESTDIR}
next reply other threads:[~2020-11-18 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 0:08 mnabid [this message]
2020-11-19 3:29 ` [PR PATCH] [Merged]: " ericonr
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-26469@inbox.vuxu.org \
--to=mnabid@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).