| Commit message (Collapse) | Author | Age |
|\
| |
| | |
buildMozillaMach: addon signing and sideloading fixes
|
| | |
|
| |
| |
| |
| | |
Fixes wrapper-installed addons, which previously rejected valid browser configurations
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html
This update includes 3 security fixes.
CVEs:
CVE-2024-1284 CVE-2024-1283
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop.html
This update includes 3 security fixes.
CVEs:
CVE-2024-1284 CVE-2024-1283
|
| | |
|
| |
| |
| |
| | |
https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/
|
| |
| |
| |
| |
| |
| | |
https://www.mozilla.org/en-US/firefox/122.0.1/releasenotes/
mozbz#1875201 is wontfix for 122
|
|\ \
| | |
| | | |
microsoft-edge: 121.0.2277.83 -> 121.0.2277.98
|
| | | |
|
|\ \ \
| | | |
| | | | |
opera: 106.0.4998.52 -> 106.0.4998.70
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The WebRTC parts of Firefox 122.0 are unconditionally linked against the
vendored libvpx that they ship with This lead to an ABI mismatch¹, when
building with --with-system-libvpx, since our libvpx version differs.
An upstream fix is expected to be shipped in Firefox 122.0.1, which is
due in the next few days.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1875201#c11
|
| |/ /
|/| |
| | |
| | | |
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
|
|\ \ \
| | | |
| | | | |
chromium: fix rust toolchain and remove M121 workaround, {ungoogled-,}chromium: 121.0.6167.85 -> 121.0.6167.139
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html
This update includes 4 security fixes.
CVEs:
CVE-2024-1060 CVE-2024-1059 CVE-2024-1077
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html
This update includes 4 security fixes.
CVEs:
CVE-2024-1060 CVE-2024-1059 CVE-2024-1077
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The rust toolchain is required for chromium since M121.
In the last major bump (M120 -> M121) we had to work around this
requirement because we hadn't had our that part of our toolchain ready.
Until now :)
So this fixes and enables the toolchain for any chromium/electron >= 121
and removes the workaround from the last major bump.
|
|\ \ \ \
| |_|/ /
|/| | | |
brave: add gtk4
|
| | | |
| | | |
| | | | |
Without this, --gtk-version=4 flag won't work on brave, which breaks ime support such as fcitx5 on wayland.
|
| |/ /
|/| |
| | |
| | | |
https://community.brave.com/t/release-channel-1-62-156/529175
|
|\ \ \
| | | |
| | | | |
buildMozillaMach: use fixed build date
|
| | | |
| | | |
| | | |
| | | | |
This makes building w/o PGO reproducible.
|
|\ \ \ \
| |/ / /
|/| | | |
microsoft-edge: 120.0.2210.144 -> 121.0.2277.83
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
librewolf-unwrapped: 122.0-1 -> 122.0-2
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html
This update includes 17 security fixes.
CVEs:
CVE-2024-0807 CVE-2024-0812 CVE-2024-0808 CVE-2024-0810 CVE-2024-0814
CVE-2024-0813 CVE-2024-0806 CVE-2024-0805 CVE-2024-0804 CVE-2024-0811
CVE-2024-0809
|
|\ \ \ \ \
| | | | | |
| | | | | | |
netsurf.buildsystem: 1.9 -> 1.10
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
buildMozillaMach: fix pgo configure flags
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This broke when support for opt-in __structuredAttrs was added in
238a6053.
Fixes: #283563
|
|\ \ \ \ \
| | | | | |
| | | | | | |
vivaldi: 6.5.3206.50 -> 6.5.3206.55
|
| | | | | | |
|
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
https://community.brave.com/t/release-channel-1-62-153/528148
|
|\ \ \ \ \
| | | | | |
| | | | | | |
librewolf-unwrapped: 121.0.1-1 -> 122.0-1
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
firefox-unwrapped: 121.0.1 -> 122.0
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://www.mozilla.org/en-US/firefox/115.7.0/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2024-02/
Fixes: CVE-2024-0741, CVE-2024-0742, CVE-2024-0746, CVE-2024-0747,
CVE-2024-0749, CVE-2024-0750, CVE-2024-0751, CVE-2024-0753,
CVE-2024-0753, CVE-2024-0755
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://www.mozilla.org/en-US/firefox/122.0/releasenotes/
https://www.mozilla.org/security/advisories/mfsa2024-01/
Fixes: CVE-2024-0741, CVE-2024-0742, CVE-2024-0743, CVE-2024-0744,
CVE-2024-0745, CVE-2024-0746, CVE-2024-0747, CVE-2024-0748,
CVE-2024-0749, CVE-2024-0750, CVE-2024-0751, CVE-2024-0752,
CVE-2024-0753, CVE-2024-0754, CVE-2024-0755
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://www.mozilla.org/en-US/firefox/122.0/releasenotes/
https://www.mozilla.org/security/advisories/mfsa2024-01/
Fixes: CVE-2024-0741, CVE-2024-0742, CVE-2024-0743, CVE-2024-0744,
CVE-2024-0745, CVE-2024-0746, CVE-2024-0747, CVE-2024-0748,
CVE-2024-0749, CVE-2024-0750, CVE-2024-0751, CVE-2024-0752,
CVE-2024-0753, CVE-2024-0754, CVE-2024-0755
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
chromium: 120.0.6099.109 -> 121.0.6167.85, google-chrome: unbreak build in M121
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This fixes the following error:
```
Running phase: installPhase
patchelf: getting info about '/nix/store/s5dybbabbwn2w7jqdv5fk0cn7jzq54b1-google-chrome-121.0.6167.85/share/google/chrome/nacl_helper': No such file or directory
```
`nacl_helper` is no longer present in the tarball since M121, so this
patch simply removes it from the hardcoded list of paths to patchelf.
I did some very brief and everything seems to work fine.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
M121 is the first version to require the new rust toolchain, which we
haven't ready yet.
Specifically, there seems to be an issue where clang looks up library
paths (with `clang_version = 17;` added to `gnFlags` (defaults to 18 and
is part of the lookup path)):
```
ninja: error: '../../../../nix/store/q5f07rqsvsxnzwbw97yi8lacksrmy13x-clang-wrapper-17.0.6/lib/clang/17/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a', needed by 'obj/third_party/protobuf/libprotoc_lib.a', missing and no known rule to make it
```
Instead of
```
/nix/store/q5f07rqsvsxnzwbw97yi8lacksrmy13x-clang-wrapper-17.0.6/lib/clang/17/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a
/nix/store/q5f07rqsvsxnzwbw97yi8lacksrmy13x-clang-wrapper-17.0.6/lib/clang/18/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a
```
it should be something like
```
/nix/store/q5f07rqsvsxnzwbw97yi8lacksrmy13x-clang-wrapper-17.0.6/resource-root/lib/linux/libclang_rt.builtins-x86_64.a
```
So to give us ever so slightly more time to figure out and fix the rust
toolchain, we revert the upstream commit, that requires the rust
toolchain.
The c++ version of the QR code generator will be gone in the next few
version bumps, meaning we can no longer work around this by then.
Again, this is only to buy us ever so slightly more time.
This could have been prepared better and ahead of the stable bump, but
we simply don't have enough chromium maintainers right now :(
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html
This update includes 17 security fixes.
CVEs:
CVE-2024-0807 CVE-2024-0812 CVE-2024-0808 CVE-2024-0810 CVE-2024-0814
CVE-2024-0813 CVE-2024-0806 CVE-2024-0805 CVE-2024-0804 CVE-2024-0811
CVE-2024-0809
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://github.com/mullvad/mullvad-browser/releases/tag/13.0.9
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
https://blog.torproject.org/new-release-tor-browser-1309/
|
| |/ / / / /
|/| | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
polypane: 17.0.0 -> 17.1.0
|