Bug#875150: Should we file a removal bug?

[Moritz Muehlenhoff]

On Wed, Sep 25, 2019 at 07:57:47AM +0200, Andreas Tille wrote:
> Hi,
> 
> On Tue, Sep 24, 2019 at 10:48:24PM +0200, Moritz Mühlenhoff wrote:
> > On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> > > Hi! It seems there is no activity on this bug, should we file a removal bug?
> > 
> > Adding the last two uploaders to CC.
> 
> ... as well as Uploaders in d/control in CC.
>  
> > Is anyone of you planning to upload a Qt5 compatible release candidate of qtiplot?
> > Otherwise we'll file a removal bug as we're closing in on the Qt5 removalnow.
> > 
> > (Upload also happen to experimental to avoid a later roundtrip through NEW when a final
> > 1.0 comes out)
> 
> While the website[1] is announcing
> 
>     2019/09/18 - QtiPlot 1.0.0-rc10 release available. New features and improvements: 
> 
> (without mentioning a Qt 5 port explicitly :-() the download area[2]
> does not contain any source download of this.  It seems upstream changed
> to a closed source model since you can only download binaries with
> restricted functionality or you need to buy a license.

Ah yes, the Sourceforge page states:

Posted 2019-02-12
QtiPlot is no longer open source, therefore your comment is out of scope. We have tried to
keep it open source as long as possible. Unfortunately this was made impossible by people
insisting to distribute prebuilt binaries for Windows, without taking into account the fact
that this was our only source of revenu allowing to finance our work.

So seems best to remove it, then.

Cheers,
        Moritz