Hi ftpmaster, Hi Helmut,

While I have been involved in the Debian Med team, who
maintained the package, I had little to no involvement in
epigrass in itself, so weight my message accordingly.

Helmut Grohne, on 2024-10-30:
> Since the suggestion bug was neither closed nor tagged in a month, silent
> consent to proceed with removal is assumed.

I agree with the conclusion of the automated tool.  While
epigrass happens to be a tool specifically tailored to deal with
epidemics and would have been invaluable four years ago, I must
agree its accumulating issues seem to have been an energy drain
for maintainers of the team.  Open RC bugs require introduction
of several non-trivial packages to the archive first; I have
spent some time on open issues to see on which front I could
help, without much success.  I did question myself whether to
adjust bug metadata to prevent removal, as a package removal
then reintroduction might incur more work for everyone, notably
further round trip through New, but thought I was not the right
person to do that as I had little involvement in the package and
did not manage to resolve much of the open issues.

In this very particular case, after the package removal, I think
that a good course of action might be to put back epigrass as a
wnpp, status RFP, to document the existing work around the
package, eventually document work that is left to do before the
package can be brought back to a suitable state for upload to
the archive.  Maybe at some point, someone with enough interest
in the software will have the energy to reintroduce it.

I suspect that if I wait for the actual removal to occur, then
I'm going to forget about proceeding.  I'm considering filling
the wnpp bug ahead of time before forgetting about doing it.
The RFP package would thus still be in the archive, hope that
won't interfere with the tooling?

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier <[email protected]>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-

Attachment: signature.asc
Description: PGP signature

Reply via email to