Bug#935350: python-qt4reactor: Qt4 removal from Bullseye
On Thu, Aug 22, 2019 at 11:55:34PM +0300, Dmitry Shachnev wrote: > On Thu, Aug 22, 2019 at 07:50:20PM +0200, Moritz Mühlenhoff wrote: > > There's a separate qt5reactor upstream source which can be packaged if > > someone needs it in the future. > > Actually it was uploaded to NEW yesterday: > > https://ftp-master.debian.org/new/qt5reactor_0.5-1.html > https://salsa.debian.org/qt-kde-team/extras/qt5reactor Filing a removal bug for src:qtreactor, then. Cheers, Moritz
Bug#935350: python-qt4reactor: Qt4 removal from Bullseye
On Thu, Aug 22, 2019 at 07:50:20PM +0200, Moritz Mühlenhoff wrote: > There's a separate qt5reactor upstream source which can be packaged if > someone needs it in the future. Actually it was uploaded to NEW yesterday: https://ftp-master.debian.org/new/qt5reactor_0.5-1.html https://salsa.debian.org/qt-kde-team/extras/qt5reactor -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#935350: python-qt4reactor: Qt4 removal from Bullseye
On Wed, Aug 21, 2019 at 11:05:11PM +0300, Dmitry Shachnev wrote: > Source: qt4reactor > Version: 1.0-1 > Severity: important > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > Hi! > > As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye > cycle, as announced in [1]. Hi Micah, qt4reactor was a one off upload and there's no reverse dependencies in the archive, shall we just remove it? There's a separate qt5reactor upstream source which can be packaged if someone needs it in the future. Cheers, Moritz
Bug#935350: python-qt4reactor: Qt4 removal from Bullseye
Source: qt4reactor Version: 1.0-1 Severity: important User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye cycle, as announced in [1]. In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Your package still uses Qt 4, via the Python bindings (PyQt4). Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt 5 / PyQt5 port of your application; - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users; - if there is a Qt 5 port that is not yet packaged, consider packaging it; - if both the Qt 4 and the Qt 5 versions already coexist in the Debian archives, consider removing the Qt 4 version. Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4. Please see [2] for the general porting instructions, and [3] for some Python-specific differences. The removal is being tracked in [4]. My intention is to bump the severity of this bug to RC soon, like it is already the case with other Qt 4 removal bugs. [1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html [2]: https://doc.qt.io/qt-5/sourcebreaks.html [3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html [4]: https://wiki.debian.org/Qt4Removal -- Dmitry Shachnev signature.asc Description: PGP signature
