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 FTBFS - epel9 has new rust-1.88, dropp chromium-134-rust-libadler2.patch
Date: Fri, 07 Aug 2026 16:08:25 GMT [thread overview]
Message-ID: <178611890507.1.7537378936775127657.rpms-chromium-cd7bcb965ccc@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : cd7bcb965cccbd6c0efe0633bb5b9cee629fd390
Author : Than Ngo <than@redhat.com>
Date : 2025-11-13T17:20:14+01:00
Stats : +0/-19 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/cd7bcb965cccbd6c0efe0633bb5b9cee629fd390?branch=epel9-next
Log:
Fix FTBFS - epel9 has new rust-1.88, dropp chromium-134-rust-libadler2.patch
---
diff --git a/chromium-134-rust-libadler2.patch b/chromium-134-rust-libadler2.patch
deleted file mode 100644
index cada806..0000000
--- a/chromium-134-rust-libadler2.patch
+++ /dev/null
@@ -1,14 +0,0 @@
-Fix warning: libadler2 not found
-
-diff -up chromium-134.0.6998.23/build/rust/std/BUILD.gn.than chromium-134.0.6998.23/build/rust/std/BUILD.gn
---- chromium-134.0.6998.23/build/rust/std/BUILD.gn.than 2025-02-24 09:47:57.560506410 +0100
-+++ chromium-134.0.6998.23/build/rust/std/BUILD.gn 2025-02-24 09:48:02.335676712 +0100
-@@ -89,7 +89,7 @@ if (toolchain_has_rust) {
- # These are no longer present in the Windows toolchain.
- stdlib_files += [
- "addr2line",
-- "adler2",
-+ "adler",
- "gimli",
- "libc",
- "memchr",
diff --git a/chromium.spec b/chromium.spec
index abbef7e..c7c70f2 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -352,10 +352,6 @@ Patch313: chromium-142-el9-rust_alloc_error_handler_should_panic.patch
# error[E0599]: no method named `is_none_or` found for enum `Option` in the current scope
Patch314: chromium-136-rust-skrifa-build-error.patch
-# build error: libadler2 not found, rust-1.86 or newer replaces adler with adler2
-# we have rust-1.86 in f41 and newer
-Patch315: chromium-134-rust-libadler2.patch
-
# add -ftrivial-auto-var-init=zero and -fwrapv
Patch316: chromium-122-clang-build-flags.patch
@@ -1045,7 +1041,6 @@ Qt6 UI for chromium.
%patch -P313 -p1 -b .el9-rust_alloc_error_handler_should_panic
%if 0%{?rhel} && 0%{?rhel} < 10
-%patch -P315 -p1 -b .rust-libadler2
%patch -P354 -p1 -b .split-threshold-for-reg-with-hint
%endif
%patch -P316 -p1 -b .clang-build-flags
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=178611890507.1.7537378936775127657.rpms-chromium-cd7bcb965ccc@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