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: updated hash file
Date: Fri, 07 Aug 2026 16:07:39 GMT [thread overview]
Message-ID: <178611885988.1.4862025601173423079.rpms-chromium-97dc450dcf7a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 97dc450dcf7a10fdab8bfb5eca94e4c973e9784b
Author : Than Ngo <than@redhat.com>
Date : 2025-04-23T10:53:44+02:00
Stats : +6/-6 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/97dc450dcf7a10fdab8bfb5eca94e4c973e9784b?branch=epel9-next
Log:
updated hash file
---
diff --git a/chromium-135.0.7049.114-clean.tar.xz.hashes b/chromium-135.0.7049.114-clean.tar.xz.hashes
new file mode 100644
index 0000000..65ba27e
--- /dev/null
+++ b/chromium-135.0.7049.114-clean.tar.xz.hashes
@@ -0,0 +1,6 @@
+MD5 (chromium-135.0.7049.114-clean.tar.xz) = 3e6d39f1413b13c0aa50a2971401c552
+SHA1 (chromium-135.0.7049.114-clean.tar.xz) = 1f774ac27b3354e518275ac2dfa12bdd46b5bd9f
+SHA224 (chromium-135.0.7049.114-clean.tar.xz) = 6ddd90b96353b3507be4c810073d510ab071f854e2cf02e13bd4f5df
+SHA256 (chromium-135.0.7049.114-clean.tar.xz) = 54f6100482e40e30734efcdd2f0e706ae8549bbd58bc6e826cbe1f048865e7b2
+SHA384 (chromium-135.0.7049.114-clean.tar.xz) = 81828bec80e7ef896b620f99e5d90278da0f2001cfa4dfab26fbb511f9bbafa34992fe132ee03fb89b213e2915958465
+SHA512 (chromium-135.0.7049.114-clean.tar.xz) = ac77aadcd0fbefbf98276c3c8653a82873936929659c86f1edd1a4a53bc819d94007a6caa9daf25e0f2007f315175530f55575925d458837ef149c62f4402bcb
diff --git a/chromium-135.0.7049.95.tar.xz.hashes b/chromium-135.0.7049.95.tar.xz.hashes
deleted file mode 100644
index aaf064f..0000000
--- a/chromium-135.0.7049.95.tar.xz.hashes
+++ /dev/null
@@ -1,6 +0,0 @@
-a4b3e165abbce1a7f059c1b8ba08c955 chromium-135.0.7049.95-clean.tar.xz
-0cfedc1c1f27059ca5c42fe6562a2e7a30b586ba chromium-135.0.7049.95-clean.tar.xz
-59120a05929b82313bf38e751f23ad91061e797750e87f02bfb67d28 chromium-135.0.7049.95-clean.tar.xz
-efb07d889d133c90e0b7b84b08727203ada1b4031f4ee29db09e192b6fdfe5f3 chromium-135.0.7049.95-clean.tar.xz
-80a89d944d9c6b6b43dcef237c07d7b2e19500eb5812b90e76d8767102aceef696fb062b4555fdc006f7cf44f519567e chromium-135.0.7049.95-clean.tar.xz
-bb73e201ebf08e05901a54ceef367de95257da49f3c090b0cc88e23af0e901ecaa13b915080f911c29a157191efd6bcab00c844a58fd3757009a89255af0ec89 chromium-135.0.7049.95-clean.tar.xz
reply other threads:[~2026-08-07 16:07 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=178611885988.1.4862025601173423079.rpms-chromium-97dc450dcf7a@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