From: c0nnard <c0nnard@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] google-chrome : update to 113.0.5672.126-1
Date: Wed, 17 May 2023 15:51:41 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43915@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
There is a new pull request by c0nnard against master on the void-packages repository
https://github.com/c0nnard/void-packages master
https://github.com/void-linux/void-packages/pull/43915
google-chrome : update to 113.0.5672.126-1
<!-- 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/43915.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-43915.patch --]
[-- Type: text/x-diff, Size: 1223 bytes --]
From cead7e746ae9b6d9dc054c86972cb585facb32f8 Mon Sep 17 00:00:00 2001
From: c0nnard <abdicheramzi@gmail.com>
Date: Wed, 17 May 2023 15:13:58 +0200
Subject: [PATCH] google-chrome : update to 113.0.5672.126-1
---
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 834c6797d68d..58e12a821110 100644
--- a/srcpkgs/google-chrome/template
+++ b/srcpkgs/google-chrome/template
@@ -1,6 +1,6 @@
# Template file for 'google-chrome'
pkgname=google-chrome
-version=112.0.5615.165
+version=113.0.5672.126
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=75af2e83ce7ac107646a74681fdf4bb30fad99dd1f2427456256780ce21faa99
+checksum=6a624904d7a7ee2ec27e637164ddddd102cc799ffa9c14a05f88762363200bf1
_license_checksum=8023b18fb5118ef65d586363e53909861bd1a9676e5eb83c20fd3ac6e33ea0be
skiprdeps="/opt/google/chrome/libqt5_shim.so"
next reply other threads:[~2023-05-17 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:51 c0nnard [this message]
2023-05-17 14:04 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43915@inbox.vuxu.org \
--to=c0nnard@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).