public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Update OS conditionals
Date: Fri, 07 Aug 2026 16:08:56 GMT [thread overview]
Message-ID: <178611893658.1.365577252443381563.rpms-chromium-4d8f337e0f6f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 4d8f337e0f6f61723b2c09aa21ef5c2665a76ee3
Author : Yaakov Selkowitz <yselkowi@redhat.com>
Date : 2026-04-28T21:11:24-04:00
Stats : +5/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/4d8f337e0f6f61723b2c09aa21ef5c2665a76ee3?branch=epel9-next
Log:
Update OS conditionals
ELN (the future RHEL 11) tracks rawhide and therefore has the latest
toolchain and libtiff. Rust 1.95 has been brought back to ELN and Fedora
stable branches, but not yet in RHEL.
---
diff --git a/chromium.spec b/chromium.spec
index 7c6f92b..7a241b8 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -213,7 +213,7 @@
%global bundlelibdrm 0
%global bundleffmpegfree 0
%global bundlefreetype 0
-%if 0%{?fedora} > 41
+%if 0%{?fedora} > 41 || 0%{?rhel} > 10
# require libtiff-4.6.1 or newer, error: use of undeclared identifier 'TIFFOpenOptionsSetMaxCumulatedMemAlloc'
%global bundlelibtiff 0
%endif
@@ -431,7 +431,7 @@ Patch357: chromium-134-type-mismatch-error.patch
# set clang_lib path
Patch358: chromium-144-rust-clanglib.patch
-# fix FTBFS with rustc 1.95 on F45
+# fix FTBFS with rustc 1.95
Patch359: chromium-147-rustc-1.95.patch
# PowerPC64 LE support
@@ -1080,7 +1080,7 @@ Qt6 UI for chromium.
%patch -P93 -p1 -b .ftbfs-csss_style_sheet
%patch -P96 -p1 -b .crabbyavif-ftbfs-old-rust
-%if 0%{?fedora} > 43
+%if 0%{?fedora} > 43 || 0%{?rhel} > 10
%patch -P97 -p1 -b .glibc-2.42-SYS_SECCOMP
%endif
@@ -1149,7 +1149,7 @@ Qt6 UI for chromium.
%patch -P352 -p1 -b .workaround_for_crash_on_BTI_capable_system
%endif
-%ifarch aarch64 && 0%{?fedora} > 40
+%ifarch aarch64 && (0%{?fedora} > 40 || 0%{?rhel} > 10)
%patch -P353 -p1 -b .duplicate-case-value
%endif
@@ -1161,7 +1161,7 @@ Qt6 UI for chromium.
%patch -P358 -p1 -b .rust-clang_lib
-%if 0%{?fedora} > 44
+%if 0%{?fedora} > 41 || 0%{?rhel} > 10
%patch -P359 -p1 -b .ftvfs-with-rustc-1.95
%endif
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=178611893658.1.365577252443381563.rpms-chromium-4d8f337e0f6f@fedoraproject.org \
--to=yselkowi@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