| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Better-denormal-check.patch | More precise checking of vector extensions | Nicholas Guriev <guriev-ns@ya.ru> | no | 2021-12-12 | ||
| Convert-endianness.patch | Provide endianness converters before writing or after reading WAV | Nicholas Guriev <guriev-ns@ya.ru> | yes | 2021-01-28 | ||
| Fix-libabsl-include.patch | Do not include libabsl.cmake if a system library is found | Nicholas Guriev <guriev-ns@ya.ru> | yes | 2021-12-11 | ||
| Ignore-sanitize-attr.patch | Do not put the no_sanitize attribute near generated declarations. -fsanitize=cfi-icall is supported only by Clang for x86 and x86_64. That is not our case. Exclude compiler_specific.h that requires hard-coded build_config.h. . This way we avoid the header blocking the build on RISC-V 64bit and other platforms. |
Nicholas Guriev <guriev-ns@ya.ru> | no | 2023-05-04 | ||
| Skip-RNNoise.patch | Ignore absent RNNoise | Nicholas Guriev <guriev-ns@ya.ru> | no | 2021-07-29 | ||
| Unbundle-libSRTP.patch | Avoid private symbols and link against system-wide libSRTP The package no longer uses outdated bundled copy of the library. The change fixes incompatibility with OpenSSL 3.0.0 or later. . The excluded code in SrtpSession looks unreachable from the call integration in Telegram Desktop. Though, I can't 100% confirm this. |
Nicholas Guriev <guriev-ns@ya.ru> | yes | 2023-05-04 | ||
| Unbundle-libyuv.patch | Prefer system-installed libyuv if available | Nicholas Guriev <guriev-ns@ya.ru> | no | 2023-06-24 | ||
| Backport-to-stable-libvpx.patch | Backport to libvpx available in Debian stable This patch disables new VP9 features for vpx < 1.10.0. | Nicholas Guriev <guriev-ns@ya.ru> | not-needed | 2022-02-05 | ||
| Remove-usage-of-AVCodecContext-reordered_opaque.patch | [PATCH] Remove usage of AVCodecContext::reordered_opaque FFmpeg has removed this field and usage of it in chromium must be removed before the ffmpeg dependency is updated. The chromium media change can be found here: https://chromium-review.googlesource.com/c/chromium/src/+/5384308 The usage of the field in webrtc seems only to be for sanity checking, so it should be just safe to remove entirely, since webrtc does not expect re-ordering at all. |
Ted Meyer <tmathmeyer@chromium.org> | no | upstream | 2024-03-20 |