Hiawatha is no longer actively maintained by the upstream developer and
there was no maintainer for this package since the original contributor
was removed in 2019.
With https://kb.cert.org/vuls/id/461364 there are three new CVEs that
will eventually be fixed, but the interest in nixpkgs is likely low
since we don't even ship a module.
Also, rearrange the GHC‐related release notes to be in order of
most likely to matter to anyone.
Co-authored-by: Wolfgang Walther <walther@technowledgy.de>
It’s questionable whether or not this worked – 32‐bit ARM in
Nixpkgs is already flaky even when cross‐compiling, and I find
it dubious whether much 32‐bit ARM hardware can build modern
GHCs in a bearable amount of time and memory – and figuring out
cross‐compilation of bootstrap GHCs will be a more sustainable way
to keep it working if anyone cares enough to.
Also, rearrange the GHC‐related release notes to be in order of
most likely to matter to anyone.
Since we're not mentioning drops of minor versions in the release notes
anyway, we also don't need to include the minor version when we drop a
whole major.
This was used for bootstrapping GHC on powerpc64le, but it's unclear
whether that actually still works. It makes no sense to pretend to
support it, when it's most likely broken, but we can't even verify.
Also the bootstrap chain will be broken once we drop GHC 8.10.7, so we
might as well drop the whole thing.
Will be replaced with a -bin build, which becomes necessary due to
upstream becoming unfeasible to build from source starting with the 12.x
release line.
An appropriate `throw` is also added, to advise users to upgrade to the
new -bin variant.
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
This affects haskelPackages.mkDerivation, ghcWithPackages and
hoogleWithPackages which means that it is not possible to re-introduce
a ghcjs derivation downstream and create a ghcjs package set with an up
to date Nixpkgs.
This package depends on a 14-year-old version of http-parser, which has
numerous security issues. The upstream also hasn't been updated in
several years, so this is a security issue to keep around.
This reduces the filtering and renaming of airgap images archives to
make the update script and builder more resilient to upstream changes.
Additionally, it reduces the code of the k3s builder.
See 1e71cad6e4/maintainers/scripts/pluginupdate-py/pluginupdate.py (L487).
This line checks the plugin's name and normalizes it before checking with `to_update`.
`to_update` is a raw list of packages you want to update.
Thus, calling `vim-plugins-updater update "package-name"` filters `current_plugin_specs`, removing all `PluginDesc` with *normalized* names that do not match `to_update`
Hence, updating something like "mini.nvim" does not work as the filter expects normalized names. Using "mini-nvim" instead works as intended
