Changelog for
chromium-108.0.5359.124-bp153.2.148.1.x86_64.rpm :
* Wed Dec 14 2022 Andreas Stieger
- Chromium 108.0.5359.124: - Chromium 108.0.5359.98 visibility- Chromium 108.0.5359.94: - Chromium 108.0.5359.71 (boo#1205871): - Chromium 107.0.5304.121 (boo#1205736) - Build with llvm15 on openSUSE:Backports:SLE-15-SP5 and up- Chromium 107.0.5304.110 (boo#1205221) - Chromium 107.0.5304.87 (boo#1204819) - Chromium 107.0.5304.68 (boo#1204732) - Chromium 106.0.5249.119 (boo#1204223) - Chromium 106.0.5249.103: - Chromium 106.0.5249.91 (boo#1203808): - Chromium 105.0.5195.127 (boo#1203419): - Chromium 105.0.5195.102 (boo#1203102): - Update chromium-symbolic.svg: this fixes bsc#1202403.- Fix quoting in chrome-wrapper, don\'t put cwd on LD_LIBRARY_PATH- Chromium 104.0.5112.101 (boo#1202509): - Re-enable our version of chrome-wrapper- Set no sandbox if root is being used (https://crbug.com/638180)- Chromium 104.0.5112.79 (boo#1202075) - Switch back to Clang so that we can use BTI on aarch64 - Chromium 103.0.5060.134 (boo#1201679): - Chromium 103.0.5060.114 (boo#1201216) - Chromium 103.0.5060.66 - Chromium 103.0.5060.53 (boo#1200783) - Chromium 102.0.5005.115 (boo#1200423) - Switch to GTK4 on TW and Leap 15.4+ (boo#1200139)- Disable ARM control flow integrity, it causes build issues at the moment- Try a different SVG (black logo on GNOME)- Removed patches: - Chromium 102.0.5001.61 (boo#1199893) - Chromium 101.0.4951.67 - Chromium 101.0.4951.64 (boo#1199409) - Chromium 101.0.4951.54 (boo#1199118)- Chromium 101.0.4951.41 (boo#1198917) - Fixes for go 1.18- Chromium 100.0.4896.127 (boo#1198509) - Chromium 100.0.4896.88 (boo#1198361) - Patches for GCC 12: - Chromium 100.0.4896.75: - Chromium 100.0.4896.60 (boo#1197680) - Update disk constraints- Chromium 99.0.4844.84: - Chromium 99.0.4844.82: - Chromium 99.0.4844.74 (boo#1197163) - Chromium 99.0.4844.51 (boo#1196641) - Chromium 98.0.4758.102 (boo#1195986) - Chromium 98.0.4758.80 (boo#1195420) - Chromium 97.0.4692.99 (boo#1194919): - Revert chromium-94-ffmpeg-roll.patch on TW: fix moved to FFmpeg- Chromium 97.0.4692.71 (boo#1194331): - Revert wayland fixes because it doesn\'t handle GPU correctly (boo#1194182)- Use GCC 11, but disable LTO (boo#1194055).- Use our own copy of the wrapper so that we can use the fixes for Wayland- Define GNU_SOURCE and fix the below patched issues- Removed patches: - Added patches: - Revert to gcc10 on TW: gcc11 is entirely broken- No auto thread LTO: linker crash on ARM- Chromium 96.0.4664.110 (boo#1193713): - Lord of the Browsers: The Two Compilers: - Ensure newer libs and LLVM is used on Leap (boo#1192310)- Explicitly BuildRequire python3-six.- Chromium 95.0.4638.69 (boo#1192184): - Chromium 95.0.4638.54 (boo#1191844): - Remove Python 2 requirement- Disable DCHECK(): that\'s for debug only- Add pipewire-do-not-typecheck-the-portal-session_handle.patch: fix WebRTC with xdg-desktop-portal 1.10- Chromium 94.0.4606.81 (boo#1191463): - Chromium 94.0.4606.54 (boo#1190765): - Add patch to fix Leap 15.2 build: - Chromium 93.0.4577.63 (boo#1190096): - Updated chromium-glibc-2.34.patch: Fix PTHREAD_STACK_MIN errors with glibc 2.34- Chromium 92.0.4515.159 (boo#1189490): - Add missing crashpad_handler (boo#1189254)- Chromium 92.0.4515.131 (boo#1189006) - Chromium 92.0.4515.107 (boo#1188590) - chromium 91.0.4472.164 (boo#1188373) - Add chromium-91-sql-standard-layout-type.patch: to fix SQL being incorrect with libstdc++ 11- fix crash upon exit boo#1186948 add chromium-91-1190561-boo1186948.patch- Chromium 91.0.4472.114 (boo#1187481) - Chromium 91.0.4472.106 - Chromium 91.0.4472.101 (boo#1187141) - Add README.SUSE- Fix aarch64 build: - Chromium 91.0.4472.77 (boo#1186458): - use asimdrdm CPU flag for aarch64 to select only more powerful buildhosts.- Chromium 90.0.4430.212 (boo#1185908) - Chromium 90.0.4430.93 (boo#1185398): - CVE-2021-21227: Insufficient data validation in V8. - CVE-2021-21232: Use after free in Dev Tools. - CVE-2021-21233: Heap buffer overflow in ANGLE. - CVE-2021-21228: Insufficient policy enforcement in extensions. - CVE-2021-21229: Incorrect security UI in downloads. - CVE-2021-21230: Type Confusion in V8. - CVE-2021-21231: Insufficient data validation in V8. - Reference: https://chromereleases.googleblog.com/2021/04/stable-channel-update-for-desktop_26.html- Chromium 90.0.4430.85 (boo#1185047): - Chromium 89.0.4389.128 (boo#1184700): - Update to 89.0.4389.114 bsc#1184256 - CVE-2021-21194: Use after free in screen capture - CVE-2021-21195: Use after free in V8 - CVE-2021-21196: Heap buffer overflow in TabStrip - CVE-2021-21197: Heap buffer overflow in TabStrip - CVE-2021-21198: Out of bounds read in IPC - CVE-2021-21199: Use Use after free in Aura- Add libva-2.11.patch to fix build with libva <2.11- Add libva-2.11-nolegacy.patch to fix build with libva 2.11- Remove x11-ozone-fix-two-edge-cases.patch- Update to 89.0.4389.90 bsc#1183515 - CVE-2021-21191: Use after free in WebRTC. - CVE-2021-21192: Heap buffer overflow in tab groups. - CVE-2021-21193: Use after free in Blink.- Update to 89.0.4389.82- Add x11-ozone-fix-two-edge-cases.patch to fix tab drag errors- Update to 89.0.4389.72 bsc#1182960 - CVE-2021-21159: Heap buffer overflow in TabStrip. - CVE-2021-21160: Heap buffer overflow in WebAudio. - CVE-2021-21161: Heap buffer overflow in TabStrip. - CVE-2021-21162: Use after free in WebRTC. - CVE-2021-21163: Insufficient data validation in Reader Mode. - CVE-2021-21164: Insufficient data validation in Chrome for iOS. - CVE-2021-21165: Object lifecycle issue in audio. - CVE-2021-21166: Object lifecycle issue in audio. - CVE-2021-21167: Use after free in bookmarks. - CVE-2021-21168: Insufficient policy enforcement in appcache. - CVE-2021-21169: Out of bounds memory access in V8. - CVE-2021-21170: Incorrect security UI in Loader. - CVE-2021-21171: Incorrect security UI in TabStrip and Navigation. - CVE-2021-21172: Insufficient policy enforcement in File System API. - CVE-2021-21173: Side-channel information leakage in Network Internals. - CVE-2021-21174: Inappropriate implementation in Referrer. - CVE-2021-21175: Inappropriate implementation in Site isolation. - CVE-2021-21176: Inappropriate implementation in full screen mode. - CVE-2021-21177: Insufficient policy enforcement in Autofill. - CVE-2021-21178: Inappropriate implementation in Compositing. - CVE-2021-21179: Use after free in Network Internals. - CVE-2021-21180: Use after free in tab search. - CVE-2020-27844: Heap buffer overflow in OpenJPEG. - CVE-2021-21181: Side-channel information leakage in autofill. - CVE-2021-21182: Insufficient policy enforcement in navigations. - CVE-2021-21183: Inappropriate implementation in performance APIs. - CVE-2021-21184: Inappropriate implementation in performance APIs. - CVE-2021-21185: Insufficient policy enforcement in extensions. - CVE-2021-21186: Insufficient policy enforcement in QR scanning. - CVE-2021-21187: Insufficient data validation in URL formatting. - CVE-2021-21188: Use after free in Blink. - CVE-2021-21189: Insufficient policy enforcement in payments. - CVE-2021-21190: Uninitialized Use in PDFium.- Added patches: - chromium-89-quiche-private.patch - chromium-89-quiche-dcheck.patch - chromium-89-skia-CropRect.patch - chromium-89-dawn-include.patch - chromium-89-webcodecs-deps.patch - chromium-89-EnumTable-crash.patch - chromium-shim_headers.patch - chromium-89-missing-cstring-header.patch - chromium-89-AXTreeSerializer-include.patch - chromium-88-gcc-fix-swiftshader-libEGL-visibility.patch (bsc#1182775)- Removed patches: - chromium-fix-char_traits.patch - build-with-pipewire-0.3.patch - chromium-79-gcc-protobuf-alignas.patch - chromium-87-CursorFactory-include.patch - chromium-87-openscreen-include.patch - chromium-88-vaapi-attribute.patch - chromium-88-ozone-deps.patch - chromium-87-webcodecs-deps.patch - chromium-88-ityp-include.patch - chromium-88-AXTreeFormatter-include.patch - chromium-88-BookmarkModelObserver-include.patch - chromium-88-federated_learning-include.patch - chromium-88-ideographicSpaceCharacter.patch - chromium-88-StringPool-include.patch - chromium-88-dawn-static.patch - chromium-88-CompositorFrameReporter-dcheck.patch- Update to 88.0.4324.182 bsc#1182358 - CVE-2021-21149: Stack overflow in Data Transfer. - CVE-2021-21150: Use after free in Downloads. - CVE-2021-21151: Use after free in Payments. - CVE-2021-21152: Heap buffer overflow in Media. - CVE-2021-21153: Stack overflow in GPU Process. - CVE-2021-21154: Heap buffer overflow in Tab Strip. - CVE-2021-21155: Heap buffer overflow in Tab Strip. - CVE-2021-21156: Heap buffer overflow in V8. - CVE-2021-21157: Use after free in Web Sockets.- Add chromium-glibc-2.33.patch: fix Sandbox with glibc 2.33 (bsc#1182233)- Update to 88.0.4324.150 bsc#1181827 - CVE-2021-21148: Heap buffer overflow in V8- Update to 88.0.4324.146 bsc#1181772 - CVE-2021-21142: Use after free in Payments - CVE-2021-21143: Heap buffer overflow in Extensions - CVE-2021-21144: Heap buffer overflow in Tab Groups. - CVE-2021-21145: Use after free in Fonts - CVE-2021-21146: Use after free in Navigation. - CVE-2021-21147: Inappropriate implementation in Skia- Update to 88.0.4324.96 bsc#1181137 - CVE-2021-21117: Insufficient policy enforcement in Cryptohome - CVE-2021-21118: Insufficient data validation in V8 - CVE-2021-21119: Use after free in Media - CVE-2021-21120: Use after free in WebSQL - CVE-2021-21121: Use after free in Omnibox - CVE-2021-21122: Use after free in Blink - CVE-2021-21123: Insufficient data validation in File System API - CVE-2021-21124: Potential user after free in Speech Recognizer - CVE-2021-21125: Insufficient policy enforcement in File System API - CVE-2020-16044: Use after free in WebRTC - CVE-2021-21126: Insufficient policy enforcement in extensions - CVE-2021-21127: Insufficient policy enforcement in extensions - CVE-2021-21128: Heap buffer overflow in Blink - CVE-2021-21129: Insufficient policy enforcement in File System API - CVE-2021-21130: Insufficient policy enforcement in File System API - CVE-2021-21131: Insufficient policy enforcement in File System API - CVE-2021-21132: Inappropriate implementation in DevTools - CVE-2021-21133: Insufficient policy enforcement in Downloads - CVE-2021-21134: Incorrect security UI in Page Info - CVE-2021-21135: Inappropriate implementation in Performance API - CVE-2021-21136: Insufficient policy enforcement in WebView - CVE-2021-21137: Inappropriate implementation in DevTools - CVE-2021-21138: Use after free in DevTools - CVE-2021-21139: Inappropriate implementation in iframe sandbox - CVE-2021-21140: Uninitialized Use in USB - CVE-2021-21141: Insufficient policy enforcement in File System API- Added patches: - chromium-88-compiler.patch - chromium-88-ozone-deps.patch - chromium-88-ityp-include.patch - chromium-88-AXTreeFormatter-include.patch - chromium-88-BookmarkModelObserver-include.patch - chromium-88-federated_learning-include.patch - chromium-88-ideographicSpaceCharacter.patch - chromium-88-StringPool-include.patch - chromium-88-dawn-static.patch - chromium-88-CompositorFrameReporter-dcheck.patch- Removed patches: - gpu-timeout.patch - chromium-87-compiler.patch - chromium-87-ServiceWorkerContainerHost-crash.patch - chromium-87-ozone-deps.patch - chromium-87-v8-icu68.patch - chromium-87-icu68.patch- Remove C++ only flags from CFLAGS- Update chromium-gcc11.patch- Comply with new Google API key rules for Derivatives- Update to 87.0.4280.141 bsc#1180645 - CVE-2021-21106: Use after free in autofill - CVE-2021-21107: Use after free in drag and drop - CVE-2021-21108: Use after free in media - CVE-2021-21109: Use after free in payments - CVE-2021-21110: Use after free in safe browsing - CVE-2021-21111: Insufficient policy enforcement in WebUI - CVE-2021-21112: Use after free in Blink - CVE-2021-21113: Heap buffer overflow in Skia - CVE-2020-16043: Insufficient data validation in networking - CVE-2021-21114: Use after free in audio - CVE-2020-15995: Out of bounds write in V8 - CVE-2021-21115: Use after free in safe browsing - CVE-2021-21116: Heap buffer overflow in audio- Use main URLs instead of redirects in master preferences- Remove useless %post and %postun- Added patches: - chromium-87-icu68.patch - chromium-87-v8-icu68.patch- Update to 87.0.4280.88 bsc#1179576 - CVE-2020-16037: Use after free in clipboard - CVE-2020-16038: Use after free in media - CVE-2020-16039: Use after free in extensions - CVE-2020-16040: Insufficient data validation in V8 - CVE-2020-16041: Out of bounds read in networking - CVE-2020-16042: Uninitialized Use in V8- Remove erroneous call to ldconfig which causes Firefox crashes (boo#1179298)- Added patches: - chromium-gcc11.patch - chromium-86-fix-vaapi-on-intel.patch - chromium-87-compiler.patch - chromium-87-CursorFactory-include.patch - chromium-87-openscreen-include.patch - chromium-87-ozone-deps.patch - chromium-87-ServiceWorkerContainerHost-crash.patch - chromium-87-webcodecs-deps.patch - chromium-88-vaapi-attribute.patch - chromium-lp152-missing-includes.patch- Removed patches: - chromium-86-ServiceWorkerRunningInfo-noexcept.patch - chromium-86-compiler.patch - fix-invalid-end-iterator-usage-in-CookieMonster.patch - old-libva.patch- Update to 87.0.4280.66 bsc#1178923 - Wayland support by default - CVE-2020-16018: Use after free in payments. - CVE-2020-16019: Inappropriate implementation in filesystem. - CVE-2020-16020: Inappropriate implementation in cryptohome. - CVE-2020-16021: Race in ImageBurner. - CVE-2020-16022: Insufficient policy enforcement in networking. - CVE-2020-16015: Insufficient data validation in WASM. R - CVE-2020-16014: Use after free in PPAPI. - CVE-2020-16023: Use after free in WebCodecs. - CVE-2020-16024: Heap buffer overflow in UI. - CVE-2020-16025: Heap buffer overflow in clipboard. - CVE-2020-16026: Use after free in WebRTC. - CVE-2020-16027: Insufficient policy enforcement in developer tools. R - CVE-2020-16028: Heap buffer overflow in WebRTC. - CVE-2020-16029: Inappropriate implementation in PDFium. - CVE-2020-16030: Insufficient data validation in Blink. - CVE-2019-8075: Insufficient data validation in Flash. - CVE-2020-16031: Incorrect security UI in tab preview. - CVE-2020-16032: Incorrect security UI in sharing. - CVE-2020-16033: Incorrect security UI in WebUSB. - CVE-2020-16034: Inappropriate implementation in WebRTC. - CVE-2020-16035: Insufficient data validation in cros-disks. - CVE-2020-16012: Side-channel information leakage in graphics. - CVE-2020-16036: Inappropriate implementation in cookies.- Update to 86.0.4240.198 bsc#1178703 - CVE-2020-16013: Inappropriate implementation in V8 - CVE-2020-16017: Use after free in site isolation- Update to 86.0.4240.193 bsc#1178630 - CVE-2020-16016: Inappropriate implementation in base.- Update to 86.0.4240.183 bsc#1178375 - CVE-2020-16004: Use after free in user interface. - CVE-2020-16005: Insufficient policy enforcement in ANGLE. - CVE-2020-16006: Inappropriate implementation in V8 - CVE-2020-16007: Insufficient data validation in installer. - CVE-2020-16008: Stack buffer overflow in WebRTC. - CVE-2020-16009: Inappropriate implementation in V8. - CVE-2020-16011: Heap buffer overflow in UI on Windows.- Update to 86.0.4240.111 bsc#1177936 - CVE-2020-16000: Inappropriate implementation in Blink. - CVE-2020-16001: Use after free in media. - CVE-2020-16002: Use after free in PDFium. - CVE-2020-15999: Heap buffer overflow in Freetype. - CVE-2020-16003: Use after free in printing.- chromium-86-f_seal.patch: F_SEAL- Remove vdpau->vaapi bridge as it breaks a lot: (fixes welcome by someone else than me) - Fix cookiemonster: - Update to 86.0.4240.75 bsc#1177408: - build with system libevent, the gn bug is no longer present- Remove TOC files to avoid warning in post and fix angle conditional- Update to 85.0.4183.121 bsc#1176791: - The egl stuff is from angle not swiftshader, thanks Fedora bsc#1176450- Add back the swiftshader folder wrt bsc#1176450- Update 85.0.4183.102 bsc#1176306: - Move swiftshader stuff to chromium folder directly bsc#1176207- Really update to .83 we accidentally included .69 beta release- Add patch trying to compile with old libdrm on Leap 15.1: - Version update to 85.0.4183.83 bsc#1175757 - Do not use libexec as we use /usr/lib as a target folder- Fix the build by removing expectation of llvm-7.0- Update to 84.0.4147.135 (bsc#1175505): - Add chromium-disable-parallel-gold.patch in order to disable broken parallel ld.gold with LTO.- Enable again LTO for x86_64 and increase memory constraints.- Use parallel WPA streaming, we will easily fit into memory constraints.- Remove memory_constrain hack for LTO.- Chromium 84.0.4147.125 (boo#1175085) - Disable wayland everywhere as it breaks headless and middle mouse copy everywhere: bsc#1174497 bsc#1175044- Update to 84.0.4147.105 (boo#1174582): - Try to fix non-wayland build for Leap builds- Update to 84.0.4147.89 bsc#1174189: - Refresh build-with-pipewire-0.3.patch to mirror similar patch by Fedora for Firefox; screen-capture wasn\'t actually working with the previous version of the patch.- Add BuildRequires: pkgconfig(libspa-2.0) when building with pipewire support to guard against potential package splitting off of pipewire-spa-devel from pipewire-devel.- Disable the LTO again as it still OOMs quite often- Add patch to work with new ffmpeg wrt bsc#1173292: - Add multimedia fix for disabled location and also try one additional patch from Debian on the same issue bsc#1173107 Update patch: - Add patch from Fedora to avoid attribute overrides in skia: - Add patch to hopefully fix bsc#1173107: - Update to 83.0.4103.116 bsc#1173251: - Reduce constraints to say 20 GB disk space is enough- Disable wayland integration on 15.x bsc#1173187 bsc#1173188 bsc#1173254- Enforce to not use system borders bsc#1173063- Update to 83.0.4103.106 bsc#1173029: - Another attempt on the location handling for Leap 15.1: - Attempt to build with wayland/ozone enabled- Enable more system libs on 15.2+- Remove the chromium-83-gcc-location-revert.patch as it is wrong approach to fix the problem- Update _constraints to match up LTO enablement- With GCC 10 released we should be able to enable LTO again- Update to 83.0.4103.97 bsc#1172496: - Add patch to not use bundled unrar: - Amend chromium-prop-codecs.patch to allow proprietary_codecs without building third_party/openh264- Add revert of location setting commit that broke build on openSUSE Leap 15.1: - Swtich to GCC 9.x on Leaps to avoid gcc bug exposed in gcc8- Add patch to fix building with new re2: - Update _constraints to avoid very slow builds seen on obs-arm-4 (probably due to swap)- Update to 83.0.4103.61 bsc#1171910: - update to 81.0.4044.138 bsc#1171247: - Add icu-v67.patch from upstream to fix build with icu v67- update to 81.0.4044.129 (boo#1170707): - Add chromium-80.0.3987.87-missing-cstdint-header.patch, chromium-80.0.3987.87-missing-string-header.patch and chromium-80.0.3987.106-missing-cstddef-header.patch in order to fix build with GCC 10.- Update to 81.0.4044.122 (boo#1170107 bsc#1171975): - Update to 81.0.4044.113 bsc#1169729: - Try to use system version of xdg-utils- Update to 81.0.4044.92 bsc#1168911: - Update to 80.0.3987.162 bsc#1168421: - Rebase build-with-pipewire-0.3.patch in order to fix patch collision.- Add chromium-missing-cstdint-header.patch, chromium-missing-cstring-header.patch, chromium-missing-cstring-header2.patch and chromium-missing-cstddef-header.patch in order to fix boo#1167465.- Use a symbolic icon for GNOME- Add patch to allow building with pipewire 0.3: - Update to 80.0.3987.149: - Do not pull in python deps except interpreter, the bundles are patched anwyays- Update to 80.0.3987.132 bsc#1165826: - Add patch trying to fix pulse audio issues with webrtc: - Update to 80.0.3987.122 bsc#1164828: - Add chromedriver binary to bindir- Drop sandbox binary as it should not be needed really bsc#1163588- Remove unused patch: - Update to 80.0.3987.100 bsc#1163484: - Update to 80.0.3987.87 bsc#1162833: - Update to 79.0.3945.130 boo#1161252: - Update to 79.0.3945.117 bsc#1160337: - Drop obsolete liboil BuildRequires.- update to 79.0.3945.88: - Update to 79.0.3945.79: - Update to 78.0.3904.108 bsc#1157269: - Fix build on aarch64 with: - Update to 78.0.3904.97 boo#1156172: - Keep just one conditional for vaapi enablement- Add more magic for zlib handling for SLE12 build- Add patch trying to build on SLE12: - Update to 78.0.3904.87 bsc#1155643: - Enable LTO again with disabled parallel LTO WPA streaming.- Disable LTO for now as it consumes ~20GB of RAM, we will reenable the feature later when some memory consumption fixes land in GCC- Adjust LDFLAGS settings for LTO to take memory-constraints into consideration- Update to 78.0.3904.70 bsc#1154806: - Use internal resources for icon and appdata- Update to 77.0.3865.120 bsc#1153660: - Added patch chromium-vaapi-fix.patch again to fix boo#1146219- update to chromium 77.0.3865.90 boo#1151229: - Add patch from Fedora for cert transparency: - Add patches from gentoo: - Update patch old-libva.patch to build on openSUSE Leap 15.0- Update to chromium 77.0.3865.75 bsc#1150425: - Update to 76.0.3809.132 bsc#1149143 CVE-2019-5869: - Added patch chromium-vaapi-fix.patch to fix boo#1146219- Update to 76.0.3809.100 bsc#1145242: - Add patches to fix few compilation issues: - Update to 76.0.3809.87 bsc#1143492: - Do not use lto flags from prjconf, we need to set them using gn buildsystem- Drop patch chromium-non-void-return.patch and just pass a cxxflags disabler for the check- Update gcc-enable-lto.patch to work on systems without the lto- Update to 75.0.3770.142 bsc#1141649: - Enable LTO for x86_64 - add gcc-enable-lto.patch and gcc-lto-rsp-clobber.patch patches.- Install manpage- Update to 75.0.3770.100: - Update to 75.0.3770.90 bsc#1137332 bsc#1138287: - Fix build with kernel 5.2 and avoid runtime crash due to pure virtual declaration: - Update old-libva.patch to make sure we build on Leap 42.3- Update to 75.0.3770.80 bsc#1137332: - Update to 74.0.3729.169: - Update to 74.0.3729.157: - Add patch to fix build on aarch64: - Update to 74.0.3729.108 bsc#1133313: - Update to 73.0.3686.103: - Add patch for pipewire build: - Update to 73.0.3683.86: - Update conditions to use system harfbuzz on TW+- Require java during build- Enable using pipewire when available- Rebase chromium-vaapi.patch to match up the Fedora one- Update to 73.0.3683.75 bsc#1129059: - Drop direct dependency on libgsm, we just need the devel- Update to 72.0.3626.121: - Update to 72.0.3626.119: - Update to 72.0.3626.109 bsc#1120892 CVE-2018-20073: - Update to 72.0.3626.96 bsc#1124936: - Provide web_browser so chromium can be installed instead of firefox.- Update to 72.0.3626.81 bsc#1123641: - Tweak fix_building_widevinecdm_with_chromium.patch to make it work again bsc#1120429- Update %arm build, but keep it disabled for now, as ld requires lots of RAM- Version update to 71.0.3578.98 bsc#1119364: - Increase %limit_build value to avoid OOM- Add patch to build on Leap 42.x: - Version update to 71.0.3578.80 bsc#1118529: - CVE-2018-17480: Out of bounds write in V8 - CVE-2018-17481: Use after frees in PDFium - CVE-2018-18335: Heap buffer overflow in Skia - CVE-2018-18336: Use after free in PDFium - CVE-2018-18337: Use after free in Blink - CVE-2018-18338: Heap buffer overflow in Canvas - CVE-2018-18339: Use after free in WebAudio - CVE-2018-18340: Use after free in MediaRecorder - CVE-2018-18341: Heap buffer overflow in Blink - CVE-2018-18342: Out of bounds write in V8 - CVE-2018-18343: Use after free in Skia - CVE-2018-18344: Inappropriate implementation in Extensions - Multiple issues in SQLite via WebSQL - CVE-2018-18345: Inappropriate implementation in Site Isolation - CVE-2018-18346: Incorrect security UI in Blink - CVE-2018-18347: Inappropriate implementation in Navigation - CVE-2018-18348: Inappropriate implementation in Omnibox - CVE-2018-18349: Insufficient policy enforcement in Blink - CVE-2018-18350: Insufficient policy enforcement in Blink - CVE-2018-18351: Insufficient policy enforcement in Navigation - CVE-2018-18352: Inappropriate implementation in Media - CVE-2018-18353: Inappropriate implementation in Network Authentication - CVE-2018-18354: Insufficient data validation in Shell Integration - CVE-2018-18355: Insufficient policy enforcement in URL Formatter - CVE-2018-18356: Use after free in Skia - CVE-2018-18357: Insufficient policy enforcement in URL Formatter - CVE-2018-18358: Insufficient policy enforcement in Proxy. - CVE-2018-18359: Out of bounds read in V8 - Inappropriate implementation in PDFium - Use after free in Extensions - Inappropriate implementation in Navigation - Insufficient policy enforcement in Navigation - Insufficient policy enforcement in URL Formatter - Various fixes from internal audits, fuzzing and other initiatives- Updated/refreshed patches: - Version update to 70.0.3538.110 bsc#1116608: - Version update to 70.0.3538.102 bsc#1115537 CVE-2018-17478 - Remove noto-emoji-fonts recommends. noto-emoji-fonts has been inactive for a long time. noto-coloremoji-fonts is the current recommended emoji fonts from noto. And noto-emoji-fonts (monochrome) disables noto-coloremoji-fonts (colorful).- Update to 70.0.3538.77: - Add patch trying to get the pkg to build with libva 1.x releases: - Add back chromium-old-glibc.patch to make sure we build on 42.3- Reduce the merge number on jumbo files to reduce memory usage bit- Update to 70.0.3538.67 bsc#1112111: - Keep blank line after autopatch to make SLE12 rpm macros happy
