Age | Commit message (Collapse) | Author | Files | Lines |
|
This was achieved using the following command:
sd 'wrapGAppsHook\b' wrapGAppsHook3 (rg -l 'wrapGAppsHook\b')
And then manually reverted the following changes:
- alias in top-level.nix
- function name in wrap-gapps-hook.sh
- comment in postFixup of at-spi2-core
- comment in gtk4
- comment in preFixup of 1password-gui/linux.nix
- comment in postFixup of qgis/unwrapped-ltr.nix and qgis/unwrapped.nix
- comment in postFixup of telegram-desktop
- comment in postFixup of fwupd
- buildCommand of mongodb-compass
- postFixup of xflux-gui
- comment in a patch in kdePackages.kde-gtk-config and plasma5Packages.kde-gtk-config
- description of programs.sway.wrapperFeatures.gtk NixOS option (manual rebuild)
|
|
|
|
treewide: fix version in changelog
|
|
|
|
floorp: 11.12.0 -> 11.12.2
|
|
|
|
brave: 1.65.114 -> 1.65.122
|
|
librewolf-unwrapped: 125.0.1-1 -> 125.0.2-1
|
|
|
|
|
|
appimageTools.wrapAppImage: remove version from `pname`
|
|
|
|
|
|
|
|
|
|
`appimageTools.wrapType2` no longer creates a binary `$out/bin/${name}` if `pname` and `version` is provided.
Derivations that have worked around this behavior with a `mv $out/bin/{${name},${pname}}` broke as a result.
This should fix most instances.
contex: #271071
|
|
|
|
|
|
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
|
|
|
|
|
|
ungoogled-chromium: 123.0.6312.122-1 -> 124.0.6367.60-1
|
|
|
|
Firefox: 125.0.1 -> 125.0.2
|
|
brave: 1.64.122 -> 1.65.114
|
|
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_16.html
This update includes 23 security fixes.
CVEs:
CVE-2024-3832 CVE-2024-3833 CVE-2024-3914 CVE-2024-3834 CVE-2024-3837
CVE-2024-3838 CVE-2024-3839 CVE-2024-3840 CVE-2024-3841 CVE-2024-3843
CVE-2024-3844 CVE-2024-3845 CVE-2024-3846 CVE-2024-3847
|
|
https://www.mozilla.org/en-US/firefox/125.0.2/releasenotes/
|
|
https://www.mozilla.org/en-US/firefox/125.0.2/releasenotes/
|
|
|
|
|
|
|
|
|
|
|
|
chromium: 123.0.6312.122 -> 124.0.6367.60, fix M124+ build by using the vendored libwebp
|
|
M124 shipped with broken `--ozone-platform-hint` flag handling, which we
rely on NIXOS_OZONE_WL (wayland) environment variable.
This resulted in chromium M124 opening as blank/transparent window under
wayland.
X11 continued to work fine, which is why our X11-only chromium VM test
did not catch this.
See https://issues.chromium.org/issues/329678163 for details.
Fortunately, the fix for that which landed in M125, applies cleanly on
M124, so we do just that and essentially backport that fix to M124.
|
|
{tor,mullvad}-browser: 13.0.13 -> 13.0.14
|
|
vivaldi: 6.6.3271.57 -> 6.6.3271.61
|
|
|
|
|
|
|
|
at least until we figure out how to use our libwebp again.
Works around the following error in the configure phase (pretty quick to
reproduce):
~~~
Running phase: configurePhase
ERROR Unresolved dependencies.
//third_party/libavif:libavif_enc(//build/toolchain/linux/unbundle:default)
needs //third_party/libwebp:libwebp_sharpyuv(//build/toolchain/linux/unbundle:default)
~~~
The lib.optionals saves us from rebuilding < M124 (ungoogled-chromium at
this HEAD and all of electron-source).
|
|
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_16.html
This update includes 23 security fixes.
CVEs:
CVE-2024-3832 CVE-2024-3833 CVE-2024-3914 CVE-2024-3834 CVE-2024-3837
CVE-2024-3838 CVE-2024-3839 CVE-2024-3840 CVE-2024-3841 CVE-2024-3843
CVE-2024-3844 CVE-2024-3845 CVE-2024-3846 CVE-2024-3847
|
|
microsoft-edge: 123.0.2420.81 -> 123.0.2420.97
|
|
firefox-{beta,devedition}{-bin}-unwrapped: 125.0b3 -> 125.0b9
|
|
https://www.mozilla.org/en-US/firefox/125.0.1/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2024-18/
Fixes: CVE-2024-3852, CVE-2024-3853, CVE-2024-3854, CVE-2024-3855,
CVE-2024-3856, CVE-2024-3857, CVE-2024-3858, CVE-2024-3859,
CVE-2024-3860, CVE-2024-3861, CVE-2024-3862, CVE-2024-3863,
CVE-2024-3302, CVE-2024-3864, CVE-2024-3865
|
|
https://www.mozilla.org/en-US/firefox/125.0.1/releasenotes/
https://www.mozilla.org/en-US/security/advisories/mfsa2024-18/
Fixes: CVE-2024-3852, CVE-2024-3853, CVE-2024-3854, CVE-2024-3855,
CVE-2024-3856, CVE-2024-3857, CVE-2024-3858, CVE-2024-3859,
CVE-2024-3860, CVE-2024-3861, CVE-2024-3862, CVE-2024-3863,
CVE-2024-3302, CVE-2024-3864, CVE-2024-3865
|
|
|
|
|
|
https://github.com/mullvad/mullvad-browser/releases/tag/13.0.14
|
|
https://blog.torproject.org/new-release-tor-browser-13014/
|