Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package chromium for openSUSE:Factory
checked in at 2025-04-24 17:25:35
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/chromium (Old)
and /work/SRC/openSUSE:Factory/.chromium.new.30101 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "chromium"
Thu Apr 24 17:25:35 2025 rev:459 rq:1272232 version:135.0.7049.95
Changes:
--------
--- /work/SRC/openSUSE:Factory/chromium/chromium.changes 2025-04-11
16:49:12.145337132 +0200
+++ /work/SRC/openSUSE:Factory/.chromium.new.30101/chromium.changes
2025-04-24 17:27:26.366183331 +0200
@@ -1,0 +2,15 @@
+Tue Apr 22 14:28:27 CEST 2025 - r...@suse.de
+
+- add patch chromium-135-gperf-output.patch from upstream
+ to fix compilation when using gperp-3.2 and above
+ which resolved the issue with the FALLTHROUGH comment
+
+-------------------------------------------------------------------
+Wed Apr 16 16:30:29 CEST 2025 - r...@suse.de
+
+- Chromium 135.0.7049.95
+ (stable release 2025-04-15) (boo#1241288)
+ * CVE-2025-3619: Heap buffer overflow in Codecs
+ * CVE-2025-3620: Use after free in USB
+
+-------------------------------------------------------------------
Old:
----
chromium-135.0.7049.84.tar.xz
New:
----
_scmsync.obsinfo
build.specials.obscpio
chromium-135-gperf-output.patch
chromium-135.0.7049.95.tar.xz
BETA DEBUG BEGIN:
New:
- add patch chromium-135-gperf-output.patch from upstream
to fix compilation when using gperp-3.2 and above
BETA DEBUG END:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ chromium.spec ++++++
--- /var/tmp/diff_new_pack.alHyJR/_old 2025-04-24 17:27:47.519070984 +0200
+++ /var/tmp/diff_new_pack.alHyJR/_new 2025-04-24 17:27:47.523071152 +0200
@@ -106,7 +106,7 @@
%define n_suffix %{nil}
%endif
Name: chromium%{n_suffix}
-Version: 135.0.7049.84
+Version: 135.0.7049.95
Release: 0
Summary: Google's open source browser project
License: BSD-3-Clause AND LGPL-2.1-or-later
@@ -157,6 +157,7 @@
Patch373: chromium-134-type-mismatch-error.patch
Patch375: chromium-131-fix-qt-ui.pach
Patch376: chromium-135-add_map_droppable.patch
+Patch377: chromium-135-gperf-output.patch
# conditionally applied patches
# patch where ffmpeg < 5
Patch1002: chromium-125-ffmpeg-5.x-reordered_opaque.patch
++++++ _scmsync.obsinfo ++++++
mtime: 1745324989
commit: 52d888bc6161c5decb5f7b7771c366c58cb28313b399ce9f2abf7e1f54e0e3e6
url: https://src.opensuse.org/chromium/chromium.git
revision: 52d888bc6161c5decb5f7b7771c366c58cb28313b399ce9f2abf7e1f54e0e3e6
projectscmsync: https://src.opensuse.org/chromium/_ObsPrj.git
++++++ chromium-135-gperf-output.patch ++++++
>From f8f21fb4aa01f75acbb12abf5ea8c263c6817141 Mon Sep 17 00:00:00 2001
From: Daniel Richard G <isk...@gmail.com>
Date: Tue, 15 Apr 2025 01:13:20 -0700
Subject: [PATCH] Don't apply /*FALLTHROUGH*/ edit to gperf 3.2 output
The gperf issue at https://savannah.gnu.org/bugs/index.php?53029
has been resolved as of the 3.2 release, and not only is the
/*FALLTHROUGH*/ comment replacement no longer needed, it now
breaks the build with "error: fallthrough annotation does not
directly precede switch label". Only do the edit for 3.1.
Bug: 40209959
Change-Id: I1f12a2a685b62d0dedb4298bc171ab4c94ec6b47
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6445471
Reviewed-by: Yuki Shiino <yukishi...@chromium.org>
Commit-Queue: Roland Bock <rb...@google.com>
Reviewed-by: Roland Bock <rb...@google.com>
Auto-Submit: Daniel Richard G. <isk...@gmail.com>
Cr-Commit-Position: refs/heads/main@{#1446962}
diff --git a/third_party/blink/renderer/build/scripts/gperf.py
b/third_party/blink/renderer/build/scripts/gperf.py
index 42630d37c5d89..bc9cc70faa271 100644
--- a/third_party/blink/renderer/build/scripts/gperf.py
+++ b/third_party/blink/renderer/build/scripts/gperf.py
@@ -35,10 +35,13 @@ def generate_gperf(gperf_path, gperf_input, gperf_args):
# https://savannah.gnu.org/bugs/index.php?53028
gperf_output = re.sub(r'\bregister ', '', gperf_output)
# -Wimplicit-fallthrough needs an explicit fallthrough statement,
- # so replace gperf's /*FALLTHROUGH*/ comment with the statement.
- # https://savannah.gnu.org/bugs/index.php?53029
- gperf_output = gperf_output.replace('/*FALLTHROUGH*/',
- ' [[fallthrough]];')
+ # so replace gperf 3.1's /*FALLTHROUGH*/ comment with the statement.
+ # https://savannah.gnu.org/bugs/index.php?53029 (fixed in 3.2)
+ if re.search(
+ r'/\* C\+\+ code produced by gperf version 3\.[01](\.\d+)?
\*/',
+ gperf_output):
+ gperf_output = gperf_output.replace('/*FALLTHROUGH*/',
+ ' [[fallthrough]];')
# -Wpointer-to-int-cast warns about casting pointers to smaller ints
# Replace {(int)(long)&(foo), bar} with
# {static_cast<int>(reinterpret_cast<uintptr_t>(&(foo)), bar}
++++++ chromium-135.0.7049.84.tar.xz -> chromium-135.0.7049.95.tar.xz ++++++
/work/SRC/openSUSE:Factory/chromium/chromium-135.0.7049.84.tar.xz
/work/SRC/openSUSE:Factory/.chromium.new.30101/chromium-135.0.7049.95.tar.xz
differ: char 15, line 1
