x11-misc/tint2: drop 17.1.3-r1 (aka, the fork, leaving the original)

This fork may have fixed a few issues but also introduced misc bugs
including some more severe ones like segmentation faults, and then
the new upstream shown no commit activity since the initial addition
in 2022.

Ultimately I do not think it makes sense to keep this fork, and we
should return to the original which is fairly solid even if not without
its own issues and a dead upstream (too). We could cherry pick some
fixes if someone really needs them (please file a downstream bug),
as long as it's nothing massive and is easy to understand to be
unlikely to introduce other issues.

Long term, it may be difficult to keep this if it breaks badly though
(unless there is a maintained fork somewhere, I do not keep up that
closely even though I use it on one old machine).

I considered just masking this version rather than remove, but I'd
rather not maintain two ebuilds nor leave one to fall into abandon.
I also never really used 17.1 nor know it well because I had it
masked locally after the trouble it gave me, so have little interest
in keeping it + fixing downstream.

bug notes:
* bug #898890: not looked into the exact cause but 17.0.2 builds
  on a llvm-musl profile for me, either 17.1.3-only or fixed by
  something else
* bug #948484: seems this was introduced in 17.1
* bug #961098: this was another 17.1-only issue (17.0.2 has
  no reference to log10) so dropping the libm patch alongside
* bug #970019: reporter said 17.0.2 is fine for them, and I've
  personally not had tint2-17.0.2 crash (ever)

Bug: https://bugs.gentoo.org/833135
Bug: https://bugs.gentoo.org/961098
Closes: https://bugs.gentoo.org/898890 (obsolete)
Closes: https://bugs.gentoo.org/948484 (obsolete)
Closes: https://bugs.gentoo.org/970019 (obsolete)
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>

0 files changed, 0 insertions, 0 deletions