Enabling Wayland support by default prevents use of XWayland on Wayland
systems, while correctly falling back to X11 when Wayland is
unavailable in the current session.
With the current packaging many people unnecessarily rely on the
`firefox` attribute, which is suggested by nixos-generate-config, which
in turn makes their Firefox use XWayland, when it shouldn't, which
causes bugs with GNOME on Wayland:
https://discourse.nixos.org/t/firefox-all-black-when-first-launched-after-login/21143
Using the Wayland-enabled Firefox was tested on pure X11 systems by
contributors on the #nix-mozilla:nixos.org room and we are confident
this change will not cause severe regressions.
Even better, people can now toggle `MOZ_ENABLE_WAYLAND=<0|1>` in their
environment to override this decision, should they feel the need to do
so.
- Last upstream code change that wasn't an upstreamed fix by a Nixpkgs maintainer in 2020-03-10
- `halide` bumps usually break it
- was broken by Halide 10.0.0, initially fix upstreamed by us but according to Hydra on 2022-04-17 it broke again on Halide 10.0.0 (and it hasn't been building on Hydra since then)
- has been reported upstream as broken again on Halide 12.0.0 (2021-05-20)
- we are now on Halide 14.0.0 with no fix merged or even PR'd
- Originally introduced for `megapixels`, which has dropped support for it due to bad results & complications with its integration
- With this dependency gone, I have no personal motivation to maintain this package either
For these reasons, I'm dropping the package from Nixpkgs.
Now that we actually do cleanups for 22.11, it's a good time to
drop these tombstones from before 22.05. For dropped kernel attributes
one NixOS release is IMHO enough as a grace period.
Percona Server for MySQL 5.6 is no more maintained due to the EOL of MySQL 5.6.
See https://www.percona.com/downloads/Percona-Server-5.6/LATEST/.
A bit hard to list all the potential security issues affecting it but CVE-2021-27928
should be one of them.
- As polymc has been hostily taken over, prismlauncher (the fork) should
be used instead
- The previous commit packages prismlauncher, this commit makes it so
that installing polymc will give an error message
This reverts commit d06207386d.
Removing aliases without warning is not ok, because it breaks a
lot of third party code, without a grace period during which the
ecosystem can adapt.
This reverts commit ba3319568d.
Removing aliases without warning is not ok, because it breaks a
lot of third party code, without a grace period during which the
ecosystem can adapt.
