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.77
Date: Fri, 07 Aug 2026 16:04:42 GMT	[thread overview]
Message-ID: <178611868296.1.12230555761681574803.rpms-chromium-e5d0c62d9dbc@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : e5d0c62d9dbc5007c84e351a998f60a87634859e
Author : Than Ngo <than@redhat.com>
Date   : 2023-02-08T11:54:20+01:00
Stats  : +5/-2 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/e5d0c62d9dbc5007c84e351a998f60a87634859e?branch=epel9-next

Log:
update to 110.0.5481.77

---
diff --git a/chromium.spec b/chromium.spec
index 7c055bc..d7d4fe9 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -228,7 +228,7 @@
 %endif
 
 Name:	chromium%{chromium_channel}
-Version: 110.0.5481.61
+Version: 110.0.5481.77
 Release: 1%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
@@ -1800,6 +1800,9 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
 %{chromium_path}/chromedriver
 
 %changelog
+* Wed Feb 08 2023 Than Ngo <than@redhat.com> - 110.0.5481.77-1
+- update to 110.0.5481.77
+
 * Sat Feb 04 2023 Than Ngo <than@redhat.com> - 110.0.5481.61-1
 - update to 110.0.5481.61
 

diff --git a/sources b/sources
index 38b873f..4166069 100644
--- a/sources
+++ b/sources
@@ -19,4 +19,4 @@ SHA512 (NotoSansSymbols2-Regular.ttf) = 2644b42c3fdccfe12395f9b61553aced169a0f1d
 SHA512 (NotoSansTibetan-Regular.ttf) = fb5a48fcaea80eebe7d692f6fcf00d59d47658a358d0ec8e046fc559873f88bd595b2da474d2826abd9e9305f3741c69058d867b1e6048f37fe7d71b5d3af36a
 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.61-clean.tar.xz) = bc655e72ca94c741eede89f66e76f7829e59bf2edc1c3b5c19271317a2061a9a6b176da90357ca73d325047cd9ba24549da29e735b96ecc31244e2c2adbe65fd
+SHA512 (chromium-110.0.5481.77-clean.tar.xz) = 67ebefa3ccbb9c03dbf78cd7818f2b80b2c1df4632b8ba9116dc4a6d7b78f30b3dbaa4fa4c09726b4c192aab5fab8ceaae026f65d6f2d2784c0027645cc76007

                 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=178611868296.1.12230555761681574803.rpms-chromium-e5d0c62d9dbc@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