Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
ungoogled-chromium, the only remaining consumer of this patch (due to
the version range), caught up with chromium.
Meaning this patch is no longer needed.
Ref: 85dfe83a86658f3fba80c050a774195f08fb378d
|
|
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_30.html
This update includes 2 security fixes.
CVEs:
CVE-2024-4331 CVE-2024-4368
|
|
vivaldi: 6.6.3271.61 -> 6.7.3329.17
|
|
brave: 1.65.122 -> 1.65.126
|
|
|
|
google-chrome: move independently of `chromium`, add jnsgruk as maintainer, remove leftover `google-chrome-{beta,dev}` code paths
|
|
|
|
|
|
chromium: 124.0.6367.91 -> 124.0.6367.118, lower version range of `--ozone-platform-hint` patch
|
|
Ref: fb10ea41b2a080cb4ecac34aa12cf056d8d3f90e
We had to apply this patch from M125 to M124 because at the time,
chromium hasn't backported this to M124 yet.
Until now!
Or at least somewhat.
124.0.6367.118 shipped and has an equivalent patch now, which means that
this patch is no longer needed.
(Ignoring the fact that it no longer applies because of this anyway)
At least on chromium.
The thing is, ungoogled-chromium hasn't caught up with chromium yet,
meaning it is still on < .118 and thus still needs that patch.
|
|
treewide: Move away from wiki.gnome.org (part 2)
|
|
They signaled interest in issue 306010.
|
|
Historically, `google-chrome` used the version info and debian package
FOD provided by `chromium`.
This was very efficient, because `chromium` uses parts of the debian
tarball for Widevine (opt-in, via `.override`).
Meaning `chromium` has to track that debian tarball with each update
anyway.
And they always release in sync.
So why keep seperate `google-chrome` from `chromium` now?
- The current `chromium` maintainers are already at capacity
maintaining `chromium` and have no time for `google-chrome`.
- `chromium` bumps become sometimes a bottleneck for `google-chrome`.
This is because `chromium` is built from source and a lot more time
consuming and significantly more complex.
- Lately, `chromium` and `google-chrome` both had an upstream issue
under wayland with `--ozone-platform-hint`, rendering it unusable.
For `chromium` we were able to patch it, since unlike `google-chrome`
it's built from source.
The `chromium` maintainers simply forgot that `google-chrome` might
have the same issue, continued to merge the PR, rendering
`google-chrome` broken.
This PR also removes primeos from `meta.maintainers` since they only
added themself to `google-chrome` because it inherited `chromium`'s
version, stating they don't actually use `google-chrome`.
Furthermore, primeos no longer maintains `chromium`.
Ref 477e7d6b60e817661632ff3a8aaf2e39c4cceadc
|
|
Those are leftovers from when `google-chrome-{beta,dev}` were removed
due to lack of maintenance in 59719f787e94f39e64e9086d08eaedd8a9e61b22.
|
|
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_30.html
This update includes 2 security fixes.
CVEs:
CVE-2024-4331 CVE-2024-4368
|
|
|
|
{tor,mullvad}-browser: fix font config patch
|
|
|
|
The wiki.gnome.org site is planned for retirement.
|
|
Firefox: 125.0.2 -> 125.0.3
|
|
|
|
The new substituteInPlace commands will fail when they don't apply,
which will avoid some issues.
|
|
https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/
|
|
https://www.mozilla.org/en-US/firefox/125.0.3/releasenotes/
|
|
|
|
|
|
{,ungoogled-}chromium: 124.0.6367.60 -> 124.0.6367.91, chromedriver: 123.0.6312.122 -> 124.0.6367.91
|
|
palemoon-bin: 33.0.2 -> 33.1.0
|
|
|
|
buildMozillaMach: expunge old assumptions
|
|
They're not autogenerated files any longer, and have been shipped as part
of the source tree since roughly Aug 2022.
Related: mozbz#1787977 ("Include configure in the tree")
Closes: #306937
|
|
|
|
|
|
Moves the MOZ_OBJDIR into a path that is ignored through .hgignore, and
the MOZBUILD_STATE_PATH outside of the source root.
Closes: #306937
|
|
|
|
Note that there's currently no release blog entry
for .91 specifically.
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_24.html
This update includes 4 security fixes.
CVEs:
CVE-2024-4058 CVE-2024-4059 CVE-2024-4060
|
|
Note that there's currently no release blog entry
for .91 specifically.
https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-desktop_24.html
This update includes 4 security fixes.
CVEs:
CVE-2024-4058 CVE-2024-4059 CVE-2024-4060
|
|
|
|
|
|
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
|
|
|
|
|