Almost all release ebuilds were removed due to bugs, with the only ebuild left (liblaretz) failing to build (#628516). No activity since Dec 2018. Multiple packages depend on obsolete qtwebkit (#684672).
Just issued a PR for the liblaretz package to fix multilib issues. It's reasonable releases were removed since there weren't any since 2014. Incidentally I'm in progress of preparing one, but that's complicated (mostly because reviewing all the changes done in 5 years and writing a proper release announcement is tedious). I can make a `_alpha1` version or something similar in the meanwhile if that works to avoid having just the -9999 versions. Dependency on the deprecated qtwebkit is harder to fix. There's a plan to alleviate that, but it will take some time (and I will probably do this after releasing the next version, otherwise it'd just never be released). Please let me know if there's anything else I could fix.
I just came across the situation with app-leechcraft/* as well. I counted 69 packages without KEYWORDs. I've just proposed a new QA policy to ban -9999 only ebuild packages. When trying to emerge leechcraft-meta I was faced with unsatisfied deps, being unable to. I guess CI tools don't catch leechcraft deps, since leechcraft packages are basically masked by missing keywords. I know you are the upstream, so is there a reason you haven't made a release? As to what you can do: you can make a snapshot ebuild to point to a specific commit and have it KEYWORDed. Please check examples such as rlottie as to how. I know you are an active proxy-maintainer, and that this is a MOUNTAIN of a task to update, but I'm looking into last-riting these packages if nothing happens to them within ~60 days. Don't hesitate to ask if you need guidance.
We've came to the conclusion that we're going to remove this. We believe that LeechCraft really belong in an overlay (possibly GURU). The effort required to update such a large number of packages exceeds the gain from having them. The only other distro packaging LC is openSUSE. We don't have any release ebuilds for over a year now, and the review on PR to readd them did not receive any reply for >3 months now. I feel like we're running in circles here. We put an effort to get the ebuilds relatively clean to commit, we commit them, new set of bugs accumulates and we don't hear any reply until we decide to last rite it.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b870833792ebf1ec8a26b04a62c213e776dad42f commit b870833792ebf1ec8a26b04a62c213e776dad42f Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-09-22 11:22:35 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-09-22 11:23:23 +0000 package.mask: Last rite app-leechcraft/*, virtual/leechcraft-* Bug: https://bugs.gentoo.org/693328 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+)
Removed.
