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 110.0.5481.100
Date: Fri, 07 Aug 2026 16:04:48 GMT [thread overview]
Message-ID: <178611868859.1.17700406847808883276.rpms-chromium-699b245c273a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 699b245c273afe416e10919d6dc0b44145552523
Author : Than Ngo <than@redhat.com>
Date : 2023-02-17T10:03:01+01:00
Stats : +6/-3 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/699b245c273afe416e10919d6dc0b44145552523?branch=epel9-next
Log:
update to 110.0.5481.100
---
diff --git a/chromium.spec b/chromium.spec
index 21ec30a..8b69478 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -235,8 +235,8 @@
%endif
Name: chromium%{chromium_channel}
-Version: 110.0.5481.77
-Release: 2%{?dist}
+Version: 110.0.5481.100
+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)
@@ -1686,6 +1686,9 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
%{chromium_path}/chromedriver
%changelog
+* Fri Feb 17 2023 Than Ngo <than@redhat.com> - 110.0.5481.100-1
+- update to 110.0.5481.100
+
* Thu Feb 16 2023 Than Ngo <than@redhat.com> - 110.0.5481.77-2
- fix #2071126, enable support V4L2 stateless decoders for aarch64 plattform
- fix prefers-color-scheme
diff --git a/sources b/sources
index 1ebeaa9..e6fcae3 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-110.0.5481.77-clean.tar.xz) = 67ebefa3ccbb9c03dbf78cd7818f2b80b2c1df4632b8ba9116dc4a6d7b78f30b3dbaa4fa4c09726b4c192aab5fab8ceaae026f65d6f2d2784c0027645cc76007
+SHA512 (chromium-110.0.5481.100-clean.tar.xz) = 6393cbed95f961aca179bd697a589cadb8e4dd6b65c362c7dec53172d66c807a1125497d981eda21b01a5aa909af2bb7b100b24c5cfb11a5c25c9832e2d993b9
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=178611868859.1.17700406847808883276.rpms-chromium-699b245c273a@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