public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: update to 111.0.5563.146
Date: Fri, 07 Aug 2026 16:04:57 GMT [thread overview]
Message-ID: <178611869768.1.11163299727355508814.rpms-chromium-b17d0b8866aa@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : b17d0b8866aae354e947dfc2d99dd5432358b875
Author : Than Ngo <than@redhat.com>
Date : 2023-03-28T16:42:19+02:00
Stats : +11/-6 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/b17d0b8866aae354e947dfc2d99dd5432358b875?branch=epel9-next
Log:
update to 111.0.5563.146
---
diff --git a/.gitignore b/.gitignore
index 600e4a2..c705ef5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -29,3 +29,5 @@
/node-v16.17.0-linux-x64.tar.xz
/node-v16.17.0-linux-arm64.tar.xz
/testupload
+/node-v19.8.1-linux-arm64.tar.xz
+/node-v19.8.1-linux-x64.tar.xz
diff --git a/chromium.spec b/chromium.spec
index 9511516..0a8e4d1 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -47,7 +47,7 @@
%global build_remoting 0
# set nodejs_version
-%global nodejs_version v16.17.0
+%global nodejs_version v19.8.1
# set version for devtoolset and gcc-toolset
%global dts_version 12
@@ -241,8 +241,8 @@
%endif
Name: chromium%{chromium_channel}
-Version: 111.0.5563.110
-Release: 2%{?dist}
+Version: 111.0.5563.146
+Release: 1%{?dist}
Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
Url: http://www.chromium.org/Home
License: BSD-3-Clause AND LGPL-2.1-or-later AND Apache-2.0 AND IJG AND MIT AND GPL-2.0-or-later AND ISC AND OpenSSL AND (MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-only)
@@ -1652,6 +1652,9 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
%{chromium_path}/chromedriver
%changelog
+* Tue Mar 28 2023 Than Ngo <than@redhat.com> - 111.0.5563.146-1
+- update to 111.0.5563.146
+
* Sat Mar 25 2023 Neal Gompa <ngompa@fedoraproject.org> - 111.0.5563.110-2
- Fix ffmpeg note in README.fedora
diff --git a/sources b/sources
index 7b58e89..939a213 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
-SHA512 (node-v16.17.0-linux-x64.tar.xz) = aedfeeb71420a7fbcb07fbc4c5d2ba74ffe4f88c15998809346a84148132ec866dbae4e848531a2a77ca41413f442e1046f981d4f188bdf667faf88069aa28cd
-SHA512 (node-v16.17.0-linux-arm64.tar.xz) = ae4aabc2389779c9e1b4a15622cae3ba50e0c313ca3d7a1dc7b2344df06ade1f303d6a75b941d37e2a0ef368cf047c862a822a893684494f55446afd6ab0610e
-SHA512 (chromium-111.0.5563.110-clean.tar.xz) = bdbbfaa5e56efb6c6258814c904016f8d4fd508b000054ebeab96568d70f2a7e06f630f4f53eeae3a49eb7ee80318d8d13a2a950e268d49f0b98c4cdb0e4c633
+SHA512 (node-v19.8.1-linux-arm64.tar.xz) = 86ff19085669e92ce7afe2fd7d4df0c5441df2d88c00f29d5463b805f3cf5625626db8aebf98349c9a495b772da1ce6d68263730018207ea98815058a1c81397
+SHA512 (node-v19.8.1-linux-x64.tar.xz) = 925c0037c6b7074d0b0245bced20d0a0d9b1300f53b808106f16b5018d763f5f5b00bc321b33fa1033d736b1e1076608da9b7fcae66aed53d27b100b1186e2c6
+SHA512 (chromium-111.0.5563.146-clean.tar.xz) = 3980af2936e81dda6723ec036acb0ee51e5248cba90973fbd202579b9d161956349851e29f5ba7dc0f82713385067ffee444c47531d235bf1420cd3f1ff914ff
reply other threads:[~2026-08-07 16:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178611869768.1.11163299727355508814.rpms-chromium-b17d0b8866aa@fedoraproject.org \
--to=than@redhat.com \
--cc=git-commits@fedoraproject.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