Bug#1081213: Should eclipse-tracecompass be removed from unstable?

Helmut Grohne helmut at subdivi.de
Fri Sep 13 15:45:48 BST 2024


Hi Sudip,

On Fri, Sep 13, 2024 at 11:37:32AM +0100, Sudip Mukherjee wrote:
> On Mon, Sep 09, 2024 at 01:07:03PM +0200, Helmut Grohne wrote:
> > I suggest removing eclipse-tracecompass from Debian for the following reasons:
> 
> Feels bad to say but that is the correct thing to do at this stage. :(
> 
> The sad part is that I know the fix but I can not do it as some members
> of Debian Java team are not accepting it.
> 
> More details of the problem at:
> https://lists.debian.org/debian-java/2022/09/msg00000.html
> https://lists.debian.org/debian-java/2022/09/msg00001.html
> 
> which has also resulted in https://bugs.debian.org/1019488 and
> https://bugs.debian.org/1019488 as the wrong metadata in the manifest file has caused this problem.

What you are saying reads as if the problem is understood, but there is
disagreement about the solution. Would you want to invest more energy
into it or rather remove it?

I think you could try one more time reconciling the opposing views and
if that proves unsuccessful you may ask the technical committee for
advice.

>From an autoremover point of view, once you mailed RC bug, you can just
close this removal suggestion bug.

In case you do not want to invest any further energy into the package,
consider reassigning the bug to ftp.debian.org using the template in the
submission mail.

I argue that doing nothing is worse than both removing and restarting
the discussion.

Thank you

Helmut



More information about the pkg-java-maintainers mailing list