Differences between revisions 62 and 65 (spanning 3 versions)
Revision 62 as of 2017-09-10 18:51:54
Size: 22179
Comment: edfbrowser: switched to qt5.
Revision 65 as of 2017-09-11 12:54:41
Size: 22139
Comment: debconf is also involved due to perl bindings
Deletions are marked like this. Additions are marked like this.
Line 99: Line 99:
 * brewtarget DebianBug:874838 -> "Hasn't seen an upload since 2014 but upstream is still active -> Qt 5 port already released upstream -> needs maintainer to package it -> see tsimonq2's [[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784453#31|response to bug 784453]]"  * brewtarget DebianBug:874838 -> Recently orphaned, just needs a QA upload updating to a new release, WIP by tsimonq2 (doesn't plan on adopting it, just updating it)
Line 117: Line 117:
 * debconf DebianBug:629405
Line 267: Line 268:
 * libgwenhywfar DebianBug:875012  * libgwenhywfar DebianBug:875012 -> required by KMyMoney -> double Qt4/Qt5

Qt4 (aka src:qt4-x11) removal

Template text to file bugs

Subject: Qt4 removal from Buster
Source: @FILLME@
User: debian-qt-kde@lists.debian.org
Usertags: qt4-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as announced in:


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support]

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.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-kde@lists.debian.org

The removal is being tracked in <https://wiki.debian.org/Qt4Removal>


Apps using Qt4

Situation of apps and libraries using Qt4

Reminder bugs filed against these packages


Extra build dependencies



  • bear 874830 -> "Only used in tests -> removed and tests disabled."

  • calligra 874841 -> Qt5 version in experimental

  • edfbrowser 874858 -> Switched to Qt5.

  • kdevelop -> 5.1 available in sid -> old binaries kept on kfreebsd-*.

  • kdevelop-python -> see above

  • kdesudo 874940 -> "This is Qt 3 -> it should be removed from the archive altogether in favor of kdesu -> see this and bug 875107" Removed, RoM

  • ksaneplugin 874986 Removed, RoM

  • kvirc 874998 -> unreleased Qt5 version is in experimental

  • libkpeople 875023 Removed, RoM, Qt5 version already available.

  • libksane 875024 Removed, RoM. Qt5 since KDE Applications 15.12

  • psi-plus-l10n 875110 Ported to Qt5

  • qtruby 875153 Removed, RoM

  • unetbootin 875218 -> Removed from the archive, QA. "Known upstream -> should take minimal effort to port -> bumped."

  • rinputd 875170 Removed, RoM