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 145.0.7632.159
Date: Fri, 07 Aug 2026 16:08:47 GMT	[thread overview]
Message-ID: <178611892733.1.13369846815569933089.rpms-chromium-36bcc5019a6d@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 36bcc5019a6d19916c1e91e73be3bf7dcbffcf6f
Author : Than Ngo <than@redhat.com>
Date   : 2026-03-04T15:53:31+01:00
Stats  : +6/-3 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/36bcc5019a6d19916c1e91e73be3bf7dcbffcf6f?branch=epel9-next

Log:
Update to 145.0.7632.159

---
diff --git a/chromium.spec b/chromium.spec
index 258c328..a4da7ab 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -262,7 +262,7 @@
 %endif
 
 Name:	chromium
-Version: 145.0.7632.116
+Version: 145.0.7632.159
 Release: 1%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
@@ -341,7 +341,7 @@ Patch136: chromium-133-workaround-system-ffmpeg-whitelist.patch
 # file conflict with old kernel on el8/el9
 Patch141: chromium-118-dma_buf_export_sync_file-conflict.patch
 
-#  fix ftbfs caused by old python-3.9 on el8
+# fix ftbfs caused by old python-3.9 on el9
 Patch142: chromium-143-python-3.9-ftbfs.patch
  
 # fix ftbfs caused by old rustc-1.88 on el9 and 10.1
@@ -1851,6 +1851,9 @@ fi
 %endif
 
 %changelog
+* Wed Mar 04 2026 Than Ngo <than@redhat.com> - 145.0.7632.159-1
+- Update to 145.0.7632.159
+
 * Tue Feb 24 2026 Than Ngo <than@redhat.com> - 145.0.7632.116-1
 - Update to 145.0.7632.116
   * CVE-2026-3061: Out of bounds read in Media

diff --git a/sources b/sources
index 17f7427..4aa2951 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
 SHA512 (rollup-linux-arm64-gnu-4.22.4.tgz) = 01d3d1a0d8b734a54ba2508dfd2a7817837577df1ce120671cc2a82ee886e915e0a19e2c965b1eb868a8b33ba69cf1a63ccd8eeea6805ff20975e0d4f1fdba03
 SHA512 (rollup-linux-powerpc64le-gnu-4.22.4.tgz) = dda5422bdc5f596d68190a53b182493c5e9b7e959f85b46785d97285a936662c852c369acb3d043f98fd5754552c003196658a4c37d2f70c91c98de1be13e83a
 SHA512 (node-v22.22.0-stripped.tar.gz) = f32a8a73063b3c78cbacf941e11dd529ebcf2618b3ba661966312e49ee9870c43a3acf256e8d331a4b0b621b16a501810c02a3ad763c75884cc250addca8e106
-SHA512 (chromium-145.0.7632.116-clean.tar.xz) = b7f3d0732b55cb4e78c70abe063deb6b3dff3f98b9f93b4cf414e3c3cd7ada83442a8db9faef84d3573e7544984ff32af5b39a63baef548d1bddc5cee363bb83
+SHA512 (chromium-145.0.7632.159-clean.tar.xz) = 0468b3a619e0dc83ded53c906ae1c1c910373bfbcc6865b49138e5af47864127c2670f037dc5ff0f0f327613928830a840524c7f5e09888de133fee9d2b4f18e

                 reply	other threads:[~2026-08-07 16:08 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=178611892733.1.13369846815569933089.rpms-chromium-36bcc5019a6d@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