From: atk <atk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] google-chrome: update to 106.0.5249.61
Date: Tue, 04 Oct 2022 09:31:42 +0200 [thread overview]
Message-ID: <20221004073142.trIGWqroiJG8NYalJOUmLNR3Tnz2v8j07Vqe9Sy-ft8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39495@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
There is an updated pull request by atk against master on the void-packages repository
https://github.com/atk/void-packages google-chrome-106.0.5249.61
https://github.com/void-linux/void-packages/pull/39495
google-chrome: update to 106.0.5249.61
replace curl with xbps-fetch
<!-- 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/39495.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-google-chrome-106.0.5249.61-39495.patch --]
[-- Type: text/x-diff, Size: 1595 bytes --]
From 4937652d1fce24951699aec1b21cbbeffe2e03f7 Mon Sep 17 00:00:00 2001
From: Alex Lohr <alexthkloss@web.de>
Date: Tue, 27 Sep 2022 21:35:08 +0200
Subject: [PATCH] google-chrome: update to 106.0.5249.91
replace curl with xbps-fetch
---
srcpkgs/google-chrome/template | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/google-chrome/template b/srcpkgs/google-chrome/template
index f260b5bd4eaa..e8b64ec61e47 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,10 +1,10 @@
# Template file for 'google-chrome'
pkgname=google-chrome
-version=105.0.5195.125
+version=106.0.5249.91
revision=1
_channel=stable
archs="x86_64"
-hostmakedepends="curl tar xz python3 python3-html2text python3-setuptools"
+hostmakedepends="tar xz python3 python3-html2text python3-setuptools"
depends="gtk+3"
short_desc="Attempt at creating a safer, faster, and more stable browser"
maintainer="Michael Aldridge <maldridge@voidlinux.org>"
@@ -20,7 +20,7 @@ _chromeUrl="${_baseUrl}/${_filename}"
_licenseUrl="https://www.google.com/intl/en/chrome/terms/"
distfiles="$_chromeUrl"
-checksum=1b167d54b289343f7e6db078d0b26505a54828e0663d033dd1307e8bca917692
+checksum=bec828c1454151be5686fbe4427a3ceb4c581ea38b7476024961b874b2d2d0b1
do_extract() {
mkdir -p ${DESTDIR}
@@ -49,6 +49,7 @@ do_install() {
}
post_install() {
- curl ${_licenseUrl} | html2text >> google-chrome-eula.md
+ xbps-fetch ${_licenseUrl} -o google-chrome-eula.html
+ cat google-chrome-eula.html | html2text >> google-chrome-eula.md
vlicense google-chrome-eula.md
}
next prev parent reply other threads:[~2022-10-04 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:57 [PR PATCH] " atk
2022-10-01 8:36 ` the-maldridge
2022-10-01 20:00 ` [PR PATCH] [Updated] " atk
2022-10-01 20:00 ` atk
2022-10-04 7:31 ` atk [this message]
2022-10-05 17:30 ` [PR PATCH] [Merged]: " abenson
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=20221004073142.trIGWqroiJG8NYalJOUmLNR3Tnz2v8j07Vqe9Sy-ft8@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).