Re: Removing Qt4 in Buster

2017-11-01 Thread Lisandro Damián Nicanor Pérez Meyer
On viernes, 27 de octubre de 2017 15:40:25 -03 Jonathan Dowland wrote: > On Fri, Oct 27, 2017 at 11:34:14AM -0300, Lisandro Damián Nicanor Pérez > > Meyer wrote: > >No, we are actively working towards removing Qt4 from the archive > >during the Buster cycle. In this case libressl might help

Re: Removing Qt4 in Buster

2017-10-28 Thread Jonathan Dowland
On Fri, Oct 27, 2017 at 08:05:53PM +0500, Andrey Rahmatullin wrote: On Fri, Oct 27, 2017 at 03:40:25PM +0100, Jonathan Dowland wrote: The rationale for keeping qt4 in the archive for me (same for gtk1, gtk2, etc.) is so that people could continue to build or run out-of-distro legacy software

Re: Removing Qt4 in Buster

2017-10-27 Thread Paul Wise
On Fri, Oct 27, 2017 at 11:05 PM, Andrey Rahmatullin wrote: > Just bundle the libs, as you would do on Windows, and you'll be fine (wrt > Qt, not wrt libc, but that's a separate problem). After all, running > software compiled on a different system was never fully supported even if > the

Re: Removing Qt4 in Buster

2017-10-27 Thread Andrey Rahmatullin
On Fri, Oct 27, 2017 at 03:40:25PM +0100, Jonathan Dowland wrote: > The rationale for keeping qt4 in the archive for me (same for gtk1, > gtk2, etc.) is so that people could continue to build or run > out-of-distro legacy software far into the future. It saddens me that I > could very likely run

Re: Removing Qt4 in Buster

2017-10-27 Thread Jonathan Dowland
On Fri, Oct 27, 2017 at 11:34:14AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: No, we are actively working towards removing Qt4 from the archive during the Buster cycle. In this case libressl might help giving it a little bit longer life, but nothing more. That's entirely up to you; but,

Re: Removing Qt4 in Buster

2017-10-27 Thread Lisandro Damián Nicanor Pérez Meyer
Hi Jonathan! On martes, 17 de octubre de 2017 08:49:58 -03 Jonathan Dowland wrote: > On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez > > Meyer wrote: > >Hi everyone! This is the required notice before starting with the mass > >bug filling in order to *try* to remove Qt4

Re: Removing Qt4 in Buster

2017-10-17 Thread Jonathan Dowland
On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Hi everyone! This is the required notice before starting with the mass bug filling in order to *try* to remove Qt4 in Buster. It has only just occurred to me that if libressl is packaged for Debian (at least

Re: Removing Qt4 in Buster

2017-09-24 Thread Sune Vuorela
On 2017-09-22, Jonathan Dowland wrote: > On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: >>Jonathan Dowland >> qtscrob > > The right thing to do here is probably to remove this from the archive. > But out of curiosity I

Re: Removing Qt4 in Buster

2017-09-22 Thread Jonathan Dowland
On Fri, Sep 22, 2017 at 02:15:44PM +0200, Emilio Pozuelo Monfort wrote: You probably want qtbase5-dev. Thank you for the hint. Mumble mumble bad package names mumble, but I'll go and read [¹] before I do anything else. ¹ http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html -- ⢀⣴⠾⠻⢶⣦⠀

Re: Removing Qt4 in Buster

2017-09-22 Thread Emilio Pozuelo Monfort
On 22/09/17 14:09, Jonathan Dowland wrote: > On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: >> Jonathan Dowland >>   qtscrob > > The right thing to do here is probably to remove this from the archive. > But out of curiosity I did look at

Re: Removing Qt4 in Buster

2017-09-22 Thread Jonathan Dowland
On Tue, Sep 05, 2017 at 03:29:31PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: Jonathan Dowland qtscrob The right thing to do here is probably to remove this from the archive. But out of curiosity I did look at porting it forward to qt5: I found someone else's patch

Removing Qt4 in Buster

2017-09-05 Thread Lisandro Damián Nicanor Pérez Meyer
Hi everyone! This is the required notice before starting with the mass bug filling in order to *try* to remove Qt4 in Buster. You can see the announcement here: We have a wiki for tracking the status in