Please vbump dev-java/velocity, then last-rite dev-java/xpath
If this is the way to go then please rather stop arch teams do unnecessary work in bug 783690. We don't two EAPIRemoval blockers for the same package.
i'm aware of this and was not sure whether close the stabilization or not. currently dev-java/velocity-1.7 depends on it. the old version of werken-xpath should be gone and the new stabilized. we have new version of velocity on the way, but idk when i'll have time to finish the ebuild as there are currently some issues with it. so i did not want this package to block the eapi removal...
Well, there are ~2000 ebuilds to go, you will likely be done before the tracker is at 0 ;)
Considering a new velocity bump needs 4 weeks in stable anyway, provided you want to keep it in stable at all, then the stabilisation still makes sense.
The bug has been referenced in the following commit(s):
Author: Miroslav Šulc <email@example.com>
AuthorDate: 2021-05-19 06:40:22 +0000
Commit: Miroslav Šulc <firstname.lastname@example.org>
CommitDate: 2021-05-19 06:40:22 +0000
profiles/package.mask: dev-java/werken-xpath last-rite
Signed-off-by: Miroslav Šulc <email@example.com>
profiles/package.mask | 5 +++++
1 file changed, 5 insertions(+)