Dear maintainer,

I suggest removing libgrokj2k from Debian for the following reasons:
 * It accumulated one RC-bug:
   + #1085165: libgrokj2k: FTBFS on armhf: ‘vreinterpret_f16_u16’ was not declared in this scope
     Last modified: 1 year, 15 days

 * It is not part of trixie or forky and is not a key package.

This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.

In case the package should be kept in unstable, please evaluate each of the
RC-bugs listed above.
 * If the bug is meant to permanently prevent the package from entering testing
   or a stable release, but this package should stay part of unstable, please
   add a usertag:

       user helmutg@debian.org
       usertags NNN + sidremove-ignore

 * If the bug no longer applies, please close it. If it is closed, check
   whether the fixed version is correct and adjust if necessary.

 * Is the bug really release-critical? If not, please downgrade.

 * If the bug still applies, please send a status update at least once a year.

Once all of the mentioned RC bugs have been acted upon in one way or another,
please close this bug.

In case the package should be removed from unstable, you may reassign this
bug report:

    Control: severity -1 normal
    Control: retitle -1 RM: libgrokj2k -- RoM; rc-buggy
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:libgrokj2k

Alternatively, you may wait a month and have it reassigned.

In case you disagree with the above, please add a wontfix tag to this bug.

    Control: tags -1 + wontfix

Doing so will also prevent automatic reassignment.

Kind regards

A tool for automatically removing packages from unstable

This bug report has been automatically filed with little human intervention.
If the filing is unclear or in error, don't hesitate to contact
Helmut Grohne <helmut@subdivi.de> for assistance.

Hello Helmut,

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.

So please, remove the package - there's simply nothing I can do to fix the situation.

Regards,
Aaron

Hello Aaron,

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.

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