Dear maintainer,

I suggest removing imexam from Debian for the following reasons:
 * It accumulated one RC-bug:
   + #1084277: imexam: FTBFS: failing tests
     Last modified: 1 year, 1 month

 * 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: imexam -- RoM; rc-buggy
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:imexam

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.

Hi Helmut,

the package is indeed RC buggy since more than a year. However, as far
as I understand upstream, while the original institution (STScI) stopped
maintenance, one of its authors wants to continue privately.

As long as there is some hope, I would still keep in unstable. I will
re-evaluate this regularly (having some connections to upstream). Once
upstream declares it abandoned I will call for removal in Debian.

Hope this is ok

Cheers

Ole

Hi Ole,

That's great to hear.

That sounds fine to me, but I suggest changing process. Your last
message on #1084277 indicates there being little hope. Would you mind
posting updates regarding your re-evaluation to that bug for the benefit
of bug squashers?

Then once you do so, the bug will have activity. Activity prevents my
autoremover from considering your package (even when the RC bug is old
otherwise). You should then close my removal suggestion bug instead of
tagging it wontfix.

Helmut