Debian Patches
Status for chromium/135.0.7049.52-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| bookworm/adler1.patch | We don't have adler2 yet: | Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/clang19.patch | no | |||||
| bookworm/constflatset.patch | work around the following by using a string_view instead of string. Let users implicitly cast to string as needed. ../../components/compose/core/browser/config.cc:49:5: error: call to consteval function 'base::MakeFixedFlatSet<std::basic_string<char>, 15UL, std::less<void>>' is not a constant expression 49 | base::MakeFixedFlatSet<std::string>({"bd", "ca", "gh", "in", "ke", "my", | ^ ../../components/compose/core/browser/config.cc:49:5: note: pointer to subobject of temporary is not a constant expression ../../components/compose/core/browser/config.cc:49:5: note: temporary created here ../../components/compose/core/browser/config.cc:53:5: error: call to consteval function 'base::MakeFixedFlatSet<std::basic_string<char>, 1UL, std::less<void>>' is not a constant expression 53 | base::MakeFixedFlatSet<std::string>({"us"}); | ^ ../../components/compose/core/browser/config.cc:53:5: note: pointer to subobject of temporary is not a constant expression ../../components/compose/core/browser/config.cc:53:5: note: temporary created here 2 errors generated. This is likely a libstdc++ issue, and can probably be dropped when switching to libc++. |
no | ||||
| bookworm/gn-allowlist.patch | Newer gn added a synonym for whitelist; but our older gn doesn't support it. |
Andres Salomon <dilinger@debian.org> | no | |||
| bookworm/gn-revert-path-exists.patch | This is a mix of commit fd011815c455976b15e31966f826628b4f9f61d4 ("don't keep use_reclient=true with .reproxy_tmp") pulled from upstream plus a revert of upstream's 49b23faa16ad14e96601aea8772c7279fcbd6b44 ("sysroot.gni: Use path_exists() rather than exec_script("dir_exists.py") in order to work on older gn that lacks path_exists(). |
no | ||||
| bookworm/libxml-parseerr.patch | ../../third_party/blink/renderer/core/xml/xsl_style_sheet_libxslt.cc:125:26: error: no matching constructor for initialization of 'XMLDocumentParserScope' XMLDocumentParserScope scope(OwnerDocument(), XSLTProcessor::GenericErrorFunc, ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/blink/renderer/core/xml/parser/xml_document_parser_scope.h:41:3: note: candidate constructor not viable: no known conversion from 'void (void *, const xmlError *)' (aka 'void (void *, const _xmlError *)') to 'xmlStructuredErrorFunc' (aka 'void (*)(void *, _xmlError *)') for 3rd argument XMLDocumentParserScope(Document*, ^ ../../third_party/blink/renderer/core/xml/parser/xml_document_parser_scope.h:40:12: note: candidate constructor not viable: requires 1 argument, but 4 were provided explicit XMLDocumentParserScope(Document*); ^ libxml 2.12 changed the API slightly. This maintains compatibility with libxml 2.9. |
Andres Salomon <dilinger@debian.org> | no | |||
| debianization/clang-version.patch | hardcode lld for whatever version of clang we're using Upstream doesn't allow overridding the linker name (other than toggling lld vs gold). |
Andres Salomon <dilinger@debian.org> | no | |||
| debianization/manpage.patch | manpage updates/fixes | Daniel Echeverry <epsilon77@gmail.com> | yes | |||
| debianization/master-preferences.patch | search for {initial,master}_preferences in /etc/chromium The default chromium behavior of checking the current binary directory for initial_preferences or master_preferences doesn't conform to debian policy. |
Andres Salomon <dilinger@debian.org> | no | |||
| debianization/sandbox.patch | debian specific instructions when no working sandbox is available | Michael Gilbert <mgilbert@debian.org> | no | |||
| debianization/swiftshader-use-llvm-16.patch | switching to llvm-16 for swiftshader | Bo Yu <tsu.yubo@gmail.com> | not-needed | 2024-12-09 | ||
| disable/android.patch | disable dependency on chrome/android | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/buildtools-libc.patch | ERROR at //build/config/BUILDCONFIG.gn:561:19: Unable to load "/chromium-135.0.7049.41/buildtools/third_party/libc++/BUILD.gn". deps += [ "//buildtools/third_party/libc++:std" ] ^------------------------------------ Since we're not building clang, we don't need this. |
no | ||||
| disable/catapult.patch | remove dependencies on third_party catapult See https://bugs.debian.org/922431 for more details, but tl;dr: we should bring this back and just get rid of the (common) minified stuff in catapult/third_party/. Stuff like chai, jszip, and node-d3 are packaged for debian already. |
Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/clang-version-check.patch | remove strict clang version check during config Chromium 107 has a strict clang version check, added in commit 8f23a2c2d14fd799813134e995c160354d75d3a0. This needs a proper fix upstream; some way to check (or specify) whether it's a distribution build, and therefore shouldn't require a particular git version of clang. For now, let's just get this building in debian. |
Andres Salomon <dilinger@debian.org> | no | |||
| disable/driver-chrome-path.patch | Disable usage of google-chrome in driver | Michel Le Bihan <michel@lebihan.pl> | no | |||
| disable/font-tests.patch | disable building font tests | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/google-api-warning.patch | disable the google api key warning when those aren't found | Michael Gilbert <mgilbert@debian.org> | no | |||
| disable/screen-ai-blob.patch | delete ~/.config/chromium/screen_ai and don't download libchromescreenai.so This fixes https://bugs.debian.org/1066910 Chromium will download libchromescreenai.so (an opaque binary blob that does OCR and other things) without warning the user when you open a PDF in "reading mode". We don't actually know what's in the binary blob, so we disable the ScreenAI service right up front (and as an added benefit, that deletes everything in ~/.config/chromium/screen_ai |
Andres Salomon <dilinger@debian.org> | no | |||
| disable/signin.patch | disable browser sign-in | no | https://raw.githubusercontent.com/Eloston/ungoogled-chromium/master/resources/patches/ungoogled-chromium/disable-signin.patch | |||
| disable/tests-swiftshader.patch | no | |||||
| disable/tests.patch | no | |||||
| disable/third-party-cookies.patch | disable third-party cookies by default This is easily configured in Settings -> Security & Privacy -> Cookies & other site data With this patch, we just change the default on a new chromium profile. |
Andres Salomon <dilinger@debian.org> | no | |||
| disable/widevine-cdm-cu.patch | Disable Widevine CDM component updater | Michel Le Bihan <michel@lebihan.pl> | no | |||
| fixes/absl-optional.patch | work around a clang bug with libstdc++ (sid version) Chromium 119 used absl's 'optional' implementation. Chromium 120 switched to aliasing absl::optional to std::optional. In theory that should be all fine and good, except for the fact that there's a bug in clang: https://github.com/llvm/llvm-project/issues/50248 This bug is worked around in libc++, but not in libstdc++. There's (so far) two types of errors we hit. The first is specifically with absl::optional::emplace() - >> gen/ui/gfx/x/randr.cc:482:13: error: no matching member function for call to 'emplace' >> data.lc.emplace(); >> ~~~~~~~~^~~~~~~ >> /usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/optional:914:2: note: candidate template ignored: requirement 'is_constructible_v<x11::RandR::NotifyEvent::Lc>' was not satisfied [with _Args = <>] >> emplace(_Args&&... __args) >> ..and a similar error with just a few calls to absl::make_optional() - >> ./../third_party/blink/renderer/core/loader/history_item.cc:185:19: error: no matching function for call to 'make_optional' >> view_state_ = absl::make_optional<ViewState>(); We can't simply revert to using absl's optional implmentation, because a) they are planning to remove it (<https://abseil.io/about/design/dropin-types>), and b) chromium devs, having switched over and viewing absl::optional and std::optional as aliases, play fast and loose with those namespace. We end up playing an ever-worsening game of whack-a-mole trying to fix build errors which are just inability to do implicit conversions. Another option (which some other distributions have chosen to do) is to simply switch to building against libc++. However, that means bundling a bunch more libraries that build statically against libc++. That's undesirable. This patch provides the option of providing a workaround for libstdc++. Instead of using the official libstdc++ header for optional, we provide our own with the is_constructible assertions removed. There's no logic changes, it just removes an assertion we _know_ is met, but the compiler too broken to know it. I just copied over /usr/include/c++/14/optional, and changed a few of the functions (where you see an '#if 0' commenting out the original function). We'll need to update this patch with major libstdc++ upgrades. hitting with gcc 12 and gcc 14: ../../optional:477: _Tp &std::_Optional_base_impl<content::DocumentAssociatedData, std::_Optional_base<content::DocumentAssociatedData>>::_M_get() [_Tp = content::DocumentAssociatedData, _Dp = std::_Optional_base<content::DocumentAssociatedData>]: Assertion 'this->_M_is_engaged()' failed. [1218/170223.662125:ERROR:elf_dynamic_array_reader.h(64)] tag not found Aborted |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/armhf-timespec.patch | fix armhf build failure: ../../media/gpu/v4l2/legacy/v4l2_video_decoder_backend_stateful.cc:446:20: error: non-constant-expression cannot be narrowed from type '__suseconds64_t' (aka 'long long') to 'long' in initializer list [-Wc++11-narrowing] 446 | .tv_nsec = timeval.tv_usec * 1000, | ^~~~~~~~~~~~~~~~~~~~~~ ../../media/gpu/v4l2/legacy/v4l2_video_decoder_backend_stateful.cc:446:20: note: insert an explicit cast to silence this issue 446 | .tv_nsec = timeval.tv_usec * 1000, | ^~~~~~~~~~~~~~~~~~~~~~ | static_cast<long>( ) 1 error generated. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/bindgen.patch | fix bindgen-related stuff Two separate but related fixes: Crabbyav1f is calling bindgen features which are not currently in bookworm or sid; --allowlist-item was added in bindgen 0.68. As far as I can tell the build.rs stuff calls allowlist_item from there as well, so these arguments may just be redundant? Hopefully I'm not breaking stuff.. Drop this for sid once bindgen gets upgraded. Also, the call to bindgen sets the path for libclang to rust_bindgen_root, which is wrong. We're already passing clang_base_path with the path to libclang, there's no reason that we'd expect libclang to be in the same directory as bindgen. That fix should probably go upstream. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/clang-rust-target.patch | On amd64, Clang defaults to generating x86_64-pc-linux-gnu, while Rust generates x86_64-unknown-linux-gnu. When ThinLTO is enabled, this leads to link errors of the form ld.lld-16: error: Linking two modules of different target triples: $C_CXX_OBJECT is 'x86_64-pc-linux-gnu' whereas $RUST_OBJECT is 'x86_64-unknown-linux-gnu' |
Daniel Richard G. <skunk@iSKUNK.ORG> | no | |||
| fixes/fix-assert-in-vnc-sessions.patch | no | |||||
| fixes/font-gc-asan.patch | This is a workaround for the various issues around fonts being garbage collected instead of manually refcounted and freed. Crashes show up when using gcc's libstdc++ but not with llvm's libc++, because apparently llvm's libc++ doesn't care if string destructors are called on invalid strings. But gcc's libstdc++ does, as does upstream's ASAN builds (which manually track/validate memory usage). So upstream created this ASAN workaround - however, GCC needs it also. This should go upstream, but in a form that selects for GCC and clang with libstdc++. Also, TODO: check if that DCHECK() is actually doing something useful on ASAN builds, or if it's optimized away and/or calling has_value() is actually truly a sanity check. upstream ASAN fixes: https://chromium-review.googlesource.com/c/chromium/src/+/5629253 |
Andres Salomon <dilinger@queued.net> | no | |||
| fixes/headless-gn.patch | don't hardcode gn path When building headless_shell, don't use the bundled gn binary; instead use the gn debian system binary. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/libsync-rk3588-panthor.patch | thirdparty: fix libsync for rk3588 panthor gpu driver Chromium will crash with panthor gpu driver on rk3588 when running with ozone wayland. There is a bug reported upstream: https://issues.chromium.org/issues/343592370 I find the fix from an upstream commit: https://chromium.googlesource.com/aosp/platform/system/core/libsync/+/941fe299d072723ddd475c173fe122a4f97b8cdf%5E%21/ diff --git a/third_party/libsync/src/sync.c b/third_party/libsync/src/sync.c index 9ed03dba88..0e9ad43822 100644 |
Jianfeng Liu <liujianfeng1994@gmail.com> | no | |||
| fixes/make-pair.patch | ../../chrome/browser/ui/webui/history/browsing_history_handler.cc:147:10: error: no viable conversion from returned value of type 'tuple<typename __decay_and_strip<const basic_string<char, char_traits<char>, allocator<char>> &>::__type, typename __decay_and_strip<basic_string<char, char_traits<char>, allocator<char>>>::__type>' (aka 'tuple<std::basic_string<char, std::char_traits<char>, std::allocator<char>>, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>') to function return type 'std::pair<std::string, std::string>' (aka 'pair<basic_string<char>, basic_string<char>>') 147 | return std::make_tuple(entry.url.spec(), base::UTF16ToUTF8(title_to_set)); I guess clang can implicitly cast from a std::tuple to a std::pair, but gcc can't? |
no | ||||
| fixes/material-utils.patch | ./../third_party/material_color_utilities/src/cpp/palettes/tones.cc:59:27: note: use function 'std::abs' instead double smallest_delta = abs(smallest_delta_hct.get_chroma() - chroma); ^~~ std::abs ../../third_party/material_color_utilities/src/cpp/palettes/tones.cc:70:9: error: use of undeclared identifier 'round' if (round(chroma) == round(smallest_delta_hct.get_chroma())) { ^ |
no | ||||
| fixes/memory-allocator-dcheck-assert-fix.patch | =================================================================== | no | ||||
| fixes/pipewire14.patch | ../../third_party/webrtc/modules/video_capture/linux/pipewire_session.cc:90:3: error: no matching function for call to 'pw_node_add_listener' 90 | pw_node_add_listener(proxy_, &node_listener_, &node_events, this); | ^~~~~~~~~~~~~~~~~~~~ /usr/include/pipewire-0.3/pipewire/node.h:189:22: note: candidate function not viable: cannot convert argument of incomplete type 'pw_proxy *' to 'struct pw_node *' for 1st argument 189 | PW_API_NODE_IMPL int pw_node_add_listener(struct pw_node *object, | ^ ~~~~~~~~~~~~~~~~~~~~~~ ../../third_party/webrtc/modules/video_capture/linux/pipewire_session.cc:122:9: error: no matching function for call to 'pw_node_enum_params' 122 | pw_node_enum_params(that->proxy_, 0, id, 0, UINT32_MAX, nullptr); | ^~~~~~~~~~~~~~~~~~~ /usr/include/pipewire-0.3/pipewire/node.h:208:22: note: candidate function not viable: cannot convert argument of incomplete type 'pw_proxy *' to 'struct pw_node *' for 1st argument 208 | PW_API_NODE_IMPL int pw_node_enum_params(struct pw_node *object, | ^ ~~~~~~~~~~~~~~~~~~~~~~ 2 errors generated. This started with pipewire 1.4.0. I initially thought that since they were calling a bunch of pw_node_* functions, they should've been requesting a pw_node rather than a pw_proxy. But it looks like casting between the two is just a thing that pipewire does (see, for example, pipewire source code's src/modules/module-protocol-pulse/manager.c calls to pw_node_enum_params()). So we fix this by casting, under the assumption that the webrtc folks actually did intend to call pw_node_* functions on a pw_proxy. |
no | ||||
| fixes/predictor-denial-of-service.patch | no | |||||
| fixes/ps-print.patch | add postscript (ps) printing capability | Salvatore Bonaccorso | no | |||
| fixes/rust-clanglib.patch | Rust adds some new clang dependencies; specifically: This is in the libclang-rt-14-dev package, but with a different (and architecture-specific) path. So we special-case linux instead of doing the same thing that upstream does w/ chromeos. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/stdatomic.patch | The #define LIBCP_STDATOMIC_H is meant to block inclusion of <stdatomic.h>, which conflicts w/ chromium's <atomic>. However, it doesn't actually block it (maybe newer clang uses a different inclusion guard symbol?). This is what clang-19 needs to block stdatomic.h. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/strlcpy.patch | fixes https://bugs.debian.org/1066235 | Andres Salomon <dilinger@debian.org> | no | |||
| fixes/updater-test.patch | and chrome/updater/BUILD.gn was still including old_updater with the same logic.. |
Andres Salomon <dilinger@debian.org> | no | |||
| fixes/widevine-locations.patch | try alternative locations for libwidevinecdm.so - $HOME/.local/lib/ (snap-friendly, see https://launchpad.net/bugs/1738149) | Olivier Tilloy <olivier.tilloy@canonical.com> | no | |||
| i386/support-i386.patch | don't disable i386 builds on linux https://chromium-review.googlesource.com/c/chromium/src/+/3583780 Chromium upstream decided to kill off i386 builds on Linux. They were goin to add a 'force_x86_support' arg, but instead "[distributions that still support i386] can patch the file." At this point, i386 on linux is completely unsupported upstream, so we're on our own with bugs. |
Andres Salomon <dilinger@debian.org> | no | |||
| ppc64le/breakpad/0001-Implement-support-for-ppc64-on-Linux.patch | [PATCH] Implement support for ppc64 on Linux This patch implements support for the ppc64 architecture on Linux systems. Notable changes include: * Modification of tests to support non-4K page sizes * minidump_writer: Determine size of stack to capture based on page size * dump_writer_common: Introduce member function GetVectorRegisters to ThreadInfo on ppc64 systems. This allows Altivec/VMX registers to be dumped like they are on OS X. linux_ptrace_dumper has been updated to utilize this function along with the ptrace mode NT_PPC_VMX. * processor/exploitability_unittest.cc: Tests were disabled on non-x86 systems. They assume the system objdump is capable of disassembling x86 binaries which is not the case on other architectures. To-do: * tools/linux/md2core has been updated as well, but functionality has not been confirmed and restoration of Altivec/VMX registers has not been implemented Note that proper functionality depends on updates to third_party/LSS that introduce PPC64 support. An in-progress patch that allows breakpad to build and run successfully is available at: https://wiki.raptorcs.com/wiki/Porting/Chromium |
Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-17 | ||
| ppc64le/core/add-ppc64-architecture-string.patch | =================================================================== | no | ||||
| ppc64le/core/add-ppc64-architecture-to-extensions.diff | =================================================================== | no | ||||
| ppc64le/core/add-ppc64-pthread-stack-size.patch | =================================================================== | no | ||||
| ppc64le/core/cargo-add-ppc64.diff | =================================================================== | no | ||||
| ppc64le/crashpad/0001-Implement-support-for-PPC64-on-Linux.patch | [PATCH] Implement support for PPC64 on Linux This patch implements support for the PPC64 architecture on Linux hosts. |
Shawn Anastasio <sanastasio@raptorengineering.com> | no | 2018-08-30 | ||
| ppc64le/fixes/fix-breakpad-compile.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-clang-selection.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-different-data-layouts.patch | When building Chromium on unstable/ppc64el with ThinLTO enabled, this error occurs in the final link: ld.lld-16: error: Linking two modules of different data layouts: $C_CXX_OBJECT is 'e-m:e-i64:64-n32:64-S128-v256:256:256-v512:512:512' whereas $RUST_LIBRARY is 'e-m:e-Fn32-i64:64-n32:64-S128-v256:256:256-v512:512:512' This is because the LLVM data layout for powerpc64le-unknown-linux-gnu has evolved over time, gaining the "Fn32" bit that specifies function pointer alignment. See the following source locations: llvm-project/clang/lib/Basic/Targets/PPC.h (class PPC64TargetInfo, under "Triple.getArch() == llvm::Triple::ppc64le") rust/compiler/rustc_target/src/spec/powerpc64le_unknown_linux_gnu.rs (note that this file was relocated in a later version) This change occurred in clang-17, and rustc followed suit in 1.73.0. Since we use an older clang and a newer rustc in our unstable build, we get an inconsistency in data layouts when targeting this particular platform. The error reported by the linker is not technically an error, however, only a warning goosed up by a --fatal-warnings flag. =================================================================== |
Daniel Richard G. <skunk@iSKUNK.ORG> | no | |||
| ppc64le/fixes/fix-partition-alloc-compile.patch | =================================================================== =================================================================== |
no | ||||
| ppc64le/fixes/fix-rust-linking.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-rustc.patch | allow ppc64le to build by using proper rustc target=================================================================== | Andres Salomon <dilinger@debian.org> | no | |||
| ppc64le/fixes/fix-study-crash.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-unknown-warning-option-messages.diff | =================================================================== | no | ||||
| ppc64le/libaom/0001-Add-ppc64-target-to-libaom.patch | [PATCH] Add ppc64 target to libaom | Shawn Anastasio <shawnanastasio@gmail.com> | no | 2019-03-10 | ||
| ppc64le/libaom/0001-Add-pregenerated-config-for-libaom-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0001-linux-seccomp-bpf-ppc64-glibc-workaround-in-SIGSYS-h.patch | [PATCH] linux/seccomp-bpf: ppc64+glibc workaround in SIGSYS handler Workaround for an apparent issue with glibc negating syscall parameters. Observed on a ppc64le machine with glibc. More investigation required. |
Shawn Anastasio <shawn@anastas.io> | no | 2019-01-15 | ||
| ppc64le/sandbox/0001-sandbox-Enable-seccomp_bpf-for-ppc64.patch | [PATCH 1/1] sandbox: Enable seccomp_bpf for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-sandbox-linux-bpf_dsl-Update-syscall-ranges-for-ppc6.patch | [PATCH 1/4] sandbox/linux/bpf_dsl: Update syscall ranges for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-sandbox-linux-Implement-partial-support-for-ppc64-sy.patch | [PATCH] sandbox/linux: Implement partial support for ppc64 syscalls and ucontext Unlike other architectures, the ppc64 files currently rely on applicable headers being provided by the system. It is sufficient for standard GNU/Linux environments, but may require expansion elsewhere. |
Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0001-sandbox-linux-Update-IsSyscallAllowed-in-broker_proc.patch | [PATCH] sandbox/linux: Update IsSyscallAllowed in broker_process.cc | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-10-23 | ||
| ppc64le/sandbox/0001-sandbox-linux-Update-syscall-helpers-lists-for-ppc64.patch | [PATCH] sandbox/linux: Update syscall helpers/lists for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-18 | ||
| ppc64le/sandbox/0001-services-service_manager-sandbox-linux-Fix-TCGETS-de.patch | [PATCH] services/service_manager/sandbox/linux: Fix TCGETS declaration on PPC64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-10 | ||
| ppc64le/sandbox/0002-sandbox-linux-bpf_dsl-Modify-seccomp_macros-to-add-s.patch | [PATCH 1/4] sandbox/linux/bpf_dsl: Modify seccomp_macros to add support for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0003-sandbox-linux-system_headers-Update-linux-seccomp-he.patch | [PATCH 3/4] sandbox/linux/system_headers: Update linux seccomp header for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0004-sandbox-linux-system_headers-Update-linux-signal-hea.patch | [PATCH 4/4] sandbox/linux/system_headers: Update linux signal header for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0005-sandbox-linux-seccomp-bpf-Add-ppc64-syscall-stub.patch | [PATCH] sandbox/linux/seccomp-bpf: Add ppc64 syscall stub | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-08-09 | ||
| ppc64le/sandbox/0005-sandbox-linux-update-unit-test-for-ppc64.patch | [PATCH 5/6] sandbox/linux: update unit test for ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-13 | ||
| ppc64le/sandbox/0006-sandbox-linux-disable-timedwait-time64-ppc64.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0007-sandbox-linux-add-ppc64-stat.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0008-sandbox-fix-ppc64le-glibc234.patch | =================================================================== | no | ||||
| ppc64le/sandbox/fix-ppc64-linux-syscalls-headers.patch | =================================================================== | no | ||||
| ppc64le/sandbox/Sandbox-linux-services-credentials.cc-PPC.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Add-PPC64-support-for-boringssl.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Force-baseline-POWER8-AltiVec-VSX-CPU-features-when-.patch | [PATCH] Force baseline POWER8 / AltiVec / VSX CPU features when on a PPC64 platform in LE mode | Timothy Pearson <tpearson@raptorengineering.com> | no | 2018-09-21 | ||
| ppc64le/third_party/0001-swiftshader-fix-build.patch | fix swiftshader build issue on ppc64el | yes | upstream | vendor, https://gitlab.raptorengineering.com/raptor-engineering-public/chromium/openpower-patches/-/blob/chromium-131/patches/ppc64le/third_party/0001-swiftshader-fix-build.patch | 2024-12-20 | |
| ppc64le/third_party/0001-third-party-hwy-wrong-include.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-angle-Include-missing-header-cstddef-in-.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-libvpx-Properly-generate-gni-on-ppc64.patch | [PATCH] third_party/libvpx: Properly generate gni on ppc64 | Shawn Anastasio <shawnanastasio@yahoo.com> | no | 2018-09-04 | ||
| ppc64le/third_party/0001-third_party-lss-Don-t-look-for-mmap2-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-pffft-Include-altivec.h-on-ppc64-with-SI.patch | [PATCH] third_party/pffft: Include altivec.h on ppc64 with SIMD enabled | Shawn Anastasio <shawn@anastas.io> | no | 2019-04-24 | ||
| ppc64le/third_party/0002-Add-PPC64-generated-files-for-boringssl.patch | =================================================================== | no | ||||
| ppc64le/third_party/0002-third_party-libvpx-Remove-bad-ppc64-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0002-third_party-lss-kernel-structs.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-libvpx-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0004-third_party-crashpad-port-curl-transport-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/0004-third_party-libvpx-work-around-ambiguous-vsx.patch | =================================================================== | no | ||||
| ppc64le/third_party/dawn-fix-ppc64le-detection.patch | =================================================================== | no | ||||
| ppc64le/third_party/skia-vsx-instructions.patch | =================================================================== | no | ||||
| ppc64le/third_party/use-sysconf-page-size-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/v8/0001-Enable-ppc64-pointer-compression.patch | =================================================================== | no | ||||
| ppc64le/v8/0002-Add-ppc64-trap-instructions.patch | =================================================================== | no | ||||
| ppc64le/webrtc/Rtc_base-system-arch.h-PPC.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-debian-clang-disable-base-musttail.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-debian-clang-disable-pa-musttail.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-third_party-libvpx-use-generic-gnu.patch | =================================================================== | no | ||||
| system/eu-strip.patch | no | |||||
| system/icu-shim.patch | allow building against system icu even when is_offical_build=true I noticed this when switching to an official build and trying to build against the system's libicu, but it may be necessary for other system libs as well. If we switch to using the bundled icu, we can see if it's possible to get rid of it. |
Andres Salomon <dilinger@debian.org> | no | |||
| system/jpeg.patch | use system jpeg library | Michael Gilbert <mgilbert@debian.org> | no | |||
| system/openjpeg.patch | no | |||||
| system/opus.patch | no | |||||
| system/rapidjson.patch | build against debian's rapidjson-dev package Due to some questionable licensing (the JSON "do not use this for evil" license), debian deletes all of third_party/angle/third_party/rapidjson even though a small portion of it falls under that license. The library is tiny and doesn't change much, so this lets chromium build against the system's rapidjson-dev header files. |
Andres Salomon <dilinger@debian.org> | no | |||
| system/rollup.patch | include debian node libs (needed for rollup) This is strictly just needed for bullseye's rollup , but may be useful later on when we drop more nodejs stuff. |
Andres Salomon <dilinger@debian.org> | no | |||
| ungoogled/disable-privacy-sandbox.patch | disable Privacy Sandbox completely https://github.com/ungoogled-software/ungoogled-chromium/blob/master/patches/core/ungoogled-chromium/disable-privacy-sandbox.patch |
no |
Showing 1 to 109 of 109 entries
All known versions for source package 'chromium'
- 135.0.7049.84-1 (sid)
- 135.0.7049.84-1~deb12u1 (bookworm-security)
- 135.0.7049.52-1 (trixie)
- 135.0.7049.52-1~deb12u1 (bookworm-proposed-updates)
- 134.0.6998.35-1~deb12u1 (bookworm)
- 120.0.6099.224-1~deb11u1 (bullseye-security, bullseye)