| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 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-lss-kernel-structs.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-swiftshader-fix-build.patch | =================================================================== | no | ||||
| ppc64le/webrtc/Rtc_base-system-arch.h-PPC.patch | =================================================================== | no | ||||
| ppc64le/third_party/0004-third_party-crashpad-port-curl-transport-ppc64.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-third_party-libvpx-use-generic-gnu.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-debian-clang-disable-skia-musttail.patch | =================================================================== | no | ||||
| ppc64le/workarounds/HACK-debian-clang-disable-base-musttail.patch | =================================================================== | 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/third_party/0002-third_party-libvpx-Remove-bad-ppc64-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-libvpx-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch | =================================================================== | no | ||||
| ppc64le/third_party/0004-third_party-libvpx-work-around-ambiguous-vsx.patch | =================================================================== | no | ||||
| ppc64le/third_party/skia-vsx-instructions.patch | =================================================================== | 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/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/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/fixes/fix-clang-selection.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-rust-linking.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-breakpad-compile.patch | =================================================================== | no | ||||
| ppc64le/fixes/fix-partition-alloc-compile.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/v8/0002-Add-ppc64-trap-instructions.patch | =================================================================== | no | ||||
| ppc64le/sandbox/fix-ppc64-linux-syscalls-headers.patch | =================================================================== | no | ||||
| ppc64le/third_party/use-sysconf-page-size-on-ppc64.patch | =================================================================== | no | ||||
| ppc64le/third_party/dawn-fix-ppc64le-detection.patch | =================================================================== | no | ||||
| ppc64le/core/add-ppc64-architecture-string.patch | =================================================================== | no | ||||
| ppc64le/core/add-ppc64-pthread-stack-size.patch | no | |||||
| ppc64le/fixes/fix-study-crash.patch | =================================================================== | no | ||||
| ppc64le/core/add-ppc64-architecture-to-extensions.diff | =================================================================== | no | ||||
| ppc64le/core/cargo-add-ppc64.diff | =================================================================== | no | ||||
| ppc64le/fixes/fix-unknown-warning-option-messages.diff | =================================================================== | no | ||||
| debianization/manpage.patch | manpage updates/fixes | Daniel Echeverry <epsilon77@gmail.com> | yes | |||
| debianization/sandbox.patch | debian specific instructions when no working sandbox is available | Michael Gilbert <mgilbert@debian.org> | no | |||
| 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/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 | |||
| fixes/ps-print.patch | add postscript (ps) printing capability | Salvatore Bonaccorso | no | |||
| fixes/widevine-revision.patch | set widevine version as undefined | Michael Gilbert <mgilbert@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 | |||
| 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/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/perfetto.patch | More simple build fixes needed by libstdc++-dev 13 | Andres Salomon <dilinger@debian.org> | no | |||
| fixes/strlcpy.patch | fixes https://bugs.debian.org/1066235 | 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/memory-allocator-dcheck-assert-fix.patch | =================================================================== | 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/highway-include-path.patch | Fix an #include path so we can use our packaged version of libhwy-dev. Reported upstream at https://issues.chromium.org/357975577 Oops, and upstream broke stuff further by "fixing" the header issue with a private .gni: ERROR at //third_party/highway/BUILD.gn:3:1: Unable to load "/chromium-128.0.6613.36/third_party/highway/src/hwy.gni". import("src/hwy.gni") ^------------------- See //third_party/distributed_point_functions/BUILD.gn:71:5: which caused the file to be included. "$dpf_highway_cpp_dir:libhwy", ^---------------------------- make[1]: *** [debian/rules:170: override_dh_auto_build-arch] Error 1 |
no | ||||
| fixes/gpu-crash.patch | =================================================================== | no | ||||
| fixes/predictor-denial-of-service.patch | no | |||||
| fixes/fix-assert-in-vnc-sessions.patch | 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 | |||
| upstream/mojo.patch | copy of missing files in content/test/data, taken from upstream git This is just cp chromium-git/content/test/data/*{html,mojom,js,ts} \ chromium-debian/content/test/data/ Upstream bug report about the missing files: https://bugs.chromium.org/p/chromium/issues/detail?id=1293630 I'm not sure how much of them are actually needed, but it's easier to just copy all of them for now. Hopefully this will be fixed upstream shortly. This copy is from chromium 130. |
no | ||||
| upstream/ruy-include.patch | commit 587c2cf8b11d3c32fa26887063eda3171a3d353e IWYU: add string for std::string diff --git a/third_party/ruy/src/ruy/profiler/instrumentation.h b/third_party/ruy/src/ruy/profiler/instrumentation.h index c4df1e6..2b15ae3 100644 |
Stephan Hartmann <stha09@googlemail.com> | no | 2023-03-31 | ||
| upstream/wayland-gbm-pixmap.patch | commit 000064171db044f98d1c9e025e16007d8269e26a [ozone/wayland] Check format supported by gbm for creating native pixmap When creating native pixmap without handle, OzonePlatform::IsNativePixmapConfigSupported should return false in wayland if gbm does not support a format. This is because gbm is the only method used when creating native pixmap without handle. Also check if format is supported by gbm in WaylandSurfaceFactory::CreateNativePixmap(). Fixed: 331796411, 365399706 Change-Id: I522601f5872e5581d5e7d8acf83419c8b2881ab7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5873796 Reviewed-by: Kramer Ge <fangzhoug@chromium.org> Commit-Queue: Orko Garai <orko@igalia.com> Cr-Commit-Position: refs/heads/main@{#1358193} commit 1fbf24a85bffd14169c7bc17db6c5120cef1c643 wayland: Check gbm device is not null Ensure gbm device returned by WaylandBufferManagerGpu is checked for null. Fixed: 368622622 Change-Id: I2b59d3c5b3e7b53bd3fff50a40a06760c48b5bd7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5879075 Reviewed-by: Shrek Shao <shrekshao@google.com> Auto-Submit: Orko Garai <orko@igalia.com> Reviewed-by: Nick Yamane <nickdiego@igalia.com> Commit-Queue: Nick Yamane <nickdiego@igalia.com> Cr-Commit-Position: refs/heads/main@{#1358439} |
Orko Garai <orko@igalia.com> | no | 2024-09-20 | ||
| upstream/blink-fix-size-assertions.patch | =================================================================== | no | ||||
| disable/tests.patch | no | |||||
| disable/tests-swiftshader.patch | 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/android.patch | disable dependency on chrome/android | Michael Gilbert <mgilbert@debian.org> | 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/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/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/driver-chrome-path.patch | Disable usage of google-chrome in driver | Michel Le Bihan <michel@lebihan.pl> | no | |||
| disable/widevine-cdm-cu.patch | Disable Widevine CDM component updater | Michel Le Bihan <michel@lebihan.pl> | 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/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 | |||
| 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/event.patch | use system libevent | Michael Gilbert <mgilbert@debian.org> | no | |||
| system/openjpeg.patch | no | |||||
| system/opus.patch | no | |||||
| system/eu-strip.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 | |||
| 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 | |||
| 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 | ||||
| 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/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-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/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/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/Sandbox-linux-services-credentials.cc-PPC.patch | =================================================================== | no | ||||
| ppc64le/sandbox/0008-sandbox-fix-ppc64le-glibc234.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-third_party-angle-Include-missing-header-cstddef-in-.patch | =================================================================== | no | ||||
| ppc64le/third_party/0001-Add-PPC64-support-for-boringssl.patch | =================================================================== | no |