| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
This fixes the patch phase.
I missed this problem in #83956.
|
|
|
|
|
|
|
|
|
| |
https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_31.html
This update includes 8 security fixes.
CVEs:
CVE-2020-6450 CVE-2020-6451 CVE-2020-6452
|
| |
|
|\
| |
| | |
tor-browser-bundle-bin: enable multimedia support by default
|
| | |
|
|\ \
| | |
| | | |
tor-browser-bundle-bin: 9.0.6 -> 9.0.7
|
| | | |
|
|\ \ \
| | | |
| | | | |
chromium: Add option to enable ozone (for Wayland)
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
brave: 1.5.112 -> 1.5.115
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
chromium: Enable swiftshader by default.
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes it possible to use chromium headless with WebGL
(e.g. for webdriver tests) without having to rebuild from source.
The upstram default is to enable, thus simply removing our disabling switch.
Also fixes #41918.
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 02ca096a85eced0d653004ae95f7cc6d8597b13e.
The clang-format binary is now included in the release tarball [0] and
we don't need to add it anymore. This fixes the following build error:
ln: failed to create symbolic link 'buildtools/linux64/clang-format': File exists
However, the build still fails a bit later in the configure phase.
[0]: https://bugs.chromium.org/p/chromium/issues/detail?id=1052503
|
| | |
| | |
| | |
| | |
| | |
| | | |
The webrtc code suffered from a race condition when used
with Pulseaudio. This lead to audio input breaking every
couple of minutes during a webrtc session.
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
chromium: 80.0.3987.132 -> 80.0.3987.149
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_18.html
This update includes 13 security fixes.
CVEs:
CVE-2020-6422 CVE-2020-6424 CVE-2020-6425 CVE-2020-6426 CVE-2020-6427
CVE-2020-6428 CVE-2020-6429 CVE-2019-20503 CVE-2020-6449
Note: The release of version 81 is currently on pause:
https://chromereleases.googleblog.com/2020/03/upcoming-chrome-and-chrome-os-releases.html
|
|/ |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
https://www.mozilla.org/en-US/firefox/74.0/releasenotes/
Co-authored-by: Daniel Frank <git@danielfrank.net>
|
|/ |
|
| |
|
|\
| |
| | |
firefox-esr-68: 68.5.0esr -> 68.6.0esr
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
chromium: Update the VA-API patch (fix #81909)
|
| | |
|
|\ \
| | |
| | | |
next: 1.4.0 -> 1.5.0
|
| |/ |
|
|\ \
| |/
|/| |
firefox: Fix AArch64 build
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* The 'arm.patch' patch doesn't apply anymore.
* The 'build-arm-libopus.patch' patch isn't required anymore.
* See the mozilla phabricator link for the added patch.
Additionally, we are now *always* undconditionally applying all patches
to all architectures. That is, unless they have undesirable
side-effects, but those might not be fit for inclusion.
By applying all patches all the time, they'll be removed or replaced
when they stop applying.
|
|\ \
| | |
| | | |
brave: 1.4.95 -> 1.4.96
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
palemoon: 28.8.2.1 -> 28.8.4
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
chromium: 80.0.3987.122 -> 80.0.3987.132
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop.html
This update includes 4 security fixes.
CVEs:
CVE-2020-6420
|
|/ / /
| | |
| | |
| | | |
https://github.com/cassidyjames/ephemeral/releases/tag/6.3.0
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The fix from 1d961a4c6d6 was unfortunately incomplete. This commit fixes
the second error [0] that occurs later during the build (the Python
script third_party/blink/renderer/bindings/scripts/generate_bindings.py
requires buildtools/linux64/clang-format).
[0]: https://github.com/NixOS/nixpkgs/pull/81016#issuecomment-591572821
|
|/ |
|