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: fix dependency for feed_response.proto
Date: Fri, 07 Aug 2026 16:05:06 GMT [thread overview]
Message-ID: <178611870676.1.3892948867174984234.rpms-chromium-a4254bb39dbd@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : a4254bb39dbd516e778c31322d535e25a795c3ee
Author : Than Ngo <than@redhat.com>
Date : 2023-04-23T16:23:43+02:00
Stats : +18/-5 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/a4254bb39dbd516e778c31322d535e25a795c3ee?branch=epel9-next
Log:
fix dependency for feed_response.proto
---
diff --git a/chromium-112-fix_deps_for_response.proto.patch b/chromium-112-fix_deps_for_response.proto.patch
new file mode 100644
index 0000000..dc6302e
--- /dev/null
+++ b/chromium-112-fix_deps_for_response.proto.patch
@@ -0,0 +1,12 @@
+diff --git a/components/feed/core/proto/BUILD.gn b/components/feed/core/proto/BUILD.gn
+index f0ec5318afb07..45b8a786de973 100644
+--- a/components/feed/core/proto/BUILD.gn
++++ b/components/feed/core/proto/BUILD.gn
+@@ -66,6 +66,7 @@ proto_library("proto_v2") {
+ "v2/wire/xsurface_content.proto",
+ "v2/xsurface.proto",
+ ]
++ proto_deps = [ ":proto_ios_shared_v2" ]
+ }
+
+ proto_library("proto_ios_shared_v2") {
diff --git a/chromium.spec b/chromium.spec
index fd2570b..65deec0 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -322,6 +322,9 @@ Patch91: chromium-108-system-opus.patch
# enable WebUIDarkMode
Patch92: chromium-113-WebUIDarkMode.patch
+# merged in 113
+Patch93: chromium-112-fix_deps_for_response.proto.patch
+
# need to explicitly include a kernel header on EL7 to support MFD_CLOEXEC, F_SEAL_SHRINK, F_ADD_SEALS, F_SEAL_SEAL
Patch100: chromium-108-el7-include-fcntl-memfd.patch
@@ -930,7 +933,8 @@ udev.
%patch -P91 -p1 -b .system-opus
%endif
-%patch -P92 -p1 -b .gtk-prefers-color-scheme
+%patch -P92 -p1 -b .WebUIDarkMod
+%patch -P93 -p1 -b .fix_deps_for_response.proto
# Fedora branded user agent
%if 0%{?fedora}
@@ -1281,13 +1285,9 @@ mkdir -p %{builddir} && cp -a %{_bindir}/gn %{builddir}/
%if %{build_headless}
# Do headless first.
-# workaround for build dependency
-%build_target %{headlessbuilddir} gen/components/feed/core/proto/v2/wire/chrome_feed_response_metadata.pb.h
%build_target %{headlessbuilddir} headless_shell
%endif
-# workaround for build dependency
-%build_target %{builddir} gen/components/feed/core/proto/v2/wire/chrome_feed_response_metadata.pb.h
%build_target %{builddir} chrome
%build_target %{builddir} chrome_sandbox
%build_target %{builddir} chromedriver
@@ -1662,6 +1662,7 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
* Sun Apr 23 2023 Than Ngo <than@redhat.com> - 112.0.5615.165-2
- make --use-gl=egl default for x11/wayland
- enable WebUIDarkMode
+- fix dependency for feed_response.proto
* Thu Apr 20 2023 Than Ngo <than@redhat.com> - 112.0.5615.165-1
- update to 112.0.5615.165
reply other threads:[~2026-08-07 16:05 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=178611870676.1.3892948867174984234.rpms-chromium-a4254bb39dbd@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