This package was broken from May until November’s ZHF due to a Git
security change. In itself, that’s a one‐line fix, but a greater
concern is that this package hasn’t been updated since 2022; there
have been many releases since, including backward‐incompatible
protocol changes:
> If you operate an XRP Ledger server, upgrade to version 1.10.0 by
> March 21 to ensure service continuity.
Since it is after March 2023 and nobody has reported this package
broken, I conclude that nobody uses it, and we should remove it until
an interested maintainer comes along.
Our current version is from March 2023; there was a release with a
critical security fix in March of this year, and another one with more
security fixes two weeks ago. The listed maintainer has been inactive
in Nixpkgs for years and it seems nobody else is stepping up to keep
this package secure and updated. Let’s drop it until that changes.
These are the last packages in the tree that depend on Boost
1.75. There hasn’t been a release since 2023; upstream have stated
in <https://github.com/libbitcoin/libbitcoin-system/issues/1234> that
they do not plan to maintain the current version, and are currently
working on a backwards‐incompatible major update.
Nothing in the tree uses these libraries. The only other software
distributions on Repology packaging them are YACP and the AUR, neither
of which has had an update since 2019. They were removed from Ubuntu
after 16.04, and have more recently been removed from [SlackBuilds.org]
and [Homebrew] with the same reasoning that they’re keeping Boost
1.75 around unnecessarily and no packaged software wants them.
[SlackBuilds.org]: 17c7d0e430
[Homebrew]: https://github.com/Homebrew/homebrew-core/pull/157427
Since these packages are also unmaintained in Nixpkgs, let’s just
drop them and if anyone wants to package the 4.x version when it’s
out they can re‐add it.
It is within our scope.
The general team consensus seems to be that it is in a similar position
to nix-ld: in-tree users should migrate away from it, but out-of-tree
users can use it as a workaround, in place of a wrapper.
