Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

[Moritz Mühlenhoff]

On Mon, Jan 20, 2020 at 08:29:16PM +0100, Moritz Mühlenhoff wrote:
> On Fri, Oct 11, 2019 at 11:12:31PM +0200, Moritz Mühlenhoff wrote:
> > On Fri, Sep 13, 2019 at 07:54:04PM +0200, Francesco Poli wrote:
> > > > Right now I see three possible "fixes" for the libgs problem:
> > > [...]
> > > > - fix the code, link to libgs during the build, as is done with all the
> > > >   other libraries qgle depends on. I do not understand why libgs is treated
> > > >   differently, there may be a reason, I just don't know. I think Laurence is
> > > >   working on that, but maybe somebody else working on gle can comment.
> > > 
> > > I think this is probably the best strategy, but, as I said, let's hear
> > > what upstream developers have to say on this.
> > > 
> > > In the meanwhile, I would like to suggest once more that you upload the
> > > fixes for the serious bug (Qt5 porting) and for the other bug (qgle
> > > segfault)!
> > 
> > Agreed, it would be good if we could move forward with the Qt5 change,
> > we've closing in on the Qt4 removal and this is one of the ~ three dozen
> > packages left.
> 
> Status update: Qt4 has now been droppped from testing, qt4 will be removed
> from unstable by end of February (along with the remaining rdeps (currently 15)).

I've now filed a removal bug for gle-graphics. It can be re-introduced when
a stable Qt5 port is available, there's plenty of time until the next freeze.

Cheers,
        Moritz