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:  don't download binary blob
Date: Fri, 07 Aug 2026 16:06:12 GMT	[thread overview]
Message-ID: <178611877278.1.7834462676073290761.rpms-chromium-79a6f286c3ba@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 79a6f286c3bad0c0a657e6525825980263104f1a
Author : Than Ngo <than@redhat.com>
Date   : 2024-03-24T12:56:51+01:00
Stats  : +18/-3 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/79a6f286c3bad0c0a657e6525825980263104f1a?branch=epel9-next

Log:
don't download binary blob

---
diff --git a/chromium-123-screen-ai-service.patch b/chromium-123-screen-ai-service.patch
new file mode 100644
index 0000000..9d28a01
--- /dev/null
+++ b/chromium-123-screen-ai-service.patch
@@ -0,0 +1,13 @@
+diff -up chromium-123.0.6312.58/chrome/browser/component_updater/screen_ai_component_installer.cc.me chromium-123.0.6312.58/chrome/browser/component_updater/screen_ai_component_installer.cc
+--- chromium-123.0.6312.58/chrome/browser/component_updater/screen_ai_component_installer.cc.me	2024-03-24 10:58:43.033885904 +0100
++++ chromium-123.0.6312.58/chrome/browser/component_updater/screen_ai_component_installer.cc	2024-03-24 11:00:38.861979740 +0100
+@@ -143,8 +143,7 @@ void ScreenAIComponentInstallerPolicy::D
+ void ManageScreenAIComponentRegistration(ComponentUpdateService* cus,
+                                          PrefService* local_state) {
+   if (screen_ai::ScreenAIInstallState::ShouldInstall(local_state)) {
+-    RegisterScreenAIComponent(cus);
+-    return;
++    // don't register the screenn ai service 
+   }
+ 
+   // Clean up.

diff --git a/chromium.spec b/chromium.spec
index 56e6768..72c5e16 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -330,8 +330,11 @@ Patch8: chromium-117-widevine-other-locations.patch
 # Tell bootstrap.py to always use the version of Python we specify
 Patch11: chromium-93.0.4577.63-py3-bootstrap.patch
 
-# debian patch, disable font-test 
+# debian patches
+# disable font-test 
 Patch20: chromium-disable-font-tests.patch
+# don't download binary blob
+Patch21: chromium-123-screen-ai-service.patch
 
 # https://gitweb.gentoo.org/repo/gentoo.git/tree/www-client/chromium/files/chromium-unbundle-zlib.patch
 Patch52: chromium-81.0.4044.92-unbundle-zlib.patch
@@ -1138,6 +1141,7 @@ udev.
 %patch -P11 -p1 -b .py3
 
 %patch -P20 -p1 -b .disable-font-test
+%patch -P21 -p1 -b .screen-ai-service
 
 %if ! %{bundleminizip}
 %patch -P52 -p1 -b .unbundle-zlib
@@ -1533,8 +1537,6 @@ CHROMIUM_CORE_GN_DEFINES+=' build_dawn_tests=false enable_perfetto_unittests=fal
 CHROMIUM_CORE_GN_DEFINES+=' disable_fieldtrial_testing_config=true'
 CHROMIUM_CORE_GN_DEFINES+=' symbol_level=%{debug_level}'
 CHROMIUM_CORE_GN_DEFINES+=' angle_has_histograms=false'
-# disable screen ai service by default
-CHROMIUM_CORE_GN_DEFINES+=' enable_screen_ai_browsertests=false enable_screen_ai_service=false'
 export CHROMIUM_CORE_GN_DEFINES
 
 # browser gn defines

                 reply	other threads:[~2026-08-07 16:06 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=178611877278.1.7834462676073290761.rpms-chromium-79a6f286c3ba@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