Control: tags -1 wontfix Hello Aaron,
On Sat, Nov 29, 2025 at 08:15:52PM +0000, Aaron Boxer wrote: > Thanks for your email. Currently there is no way for me to fix any code bugs > as my mentor no longer responds to my emails and I was unable to interest a > new mentor in helping me upload fixes to unstable. This is bad and should not be a reason to remove a package. The autoremoval is meant to get rid of packages where there is a lack of interest in fixing. While I see your upload to mentors on the bug log, the package has since been recycled from mentors.d.n. Additionally, the referenced git repository appears to not have been updated beyond what is in unstable in debian/changelog. At this time, attempting to sponsor your changes is not actionable. > So please, remove the package - there's simply nothing I can do to fix the > situation. If you are still interested in the package, please provide the proposed changes once more. libgrok2j presently has four RC bugs. Two of them are about missing dependencies and are trivially fixable if the two FTBFS bugs get resolved. The armhf one has a patch at least. That leaves the CMake one. All in all, this does not look insurmountable to me. Helmut
