Differences between revisions 53 and 54
Revision 53 as of 2016-03-05 12:21:40
Size: 5909
Editor: ?DmitryShachnev
Comment: template: Fix website link and drop Severity: wishlist
Revision 54 as of 2016-03-05 13:36:50
Size: 6244
Editor: ?DmitryShachnev
Comment: Add some new bugs
Deletions are marked like this. Additions are marked like this.
Line 66: Line 66:
 * bibletime DebianBug:816804
Line 68: Line 69:
 * camitk DebianBug:816805
Line 76: Line 78:
 * fotowall DebianBug:816806
Line 78: Line 81:
 * gazebo DebianBug:816800
 * gofigure2 DebianBug:816807
Line 79: Line 84:
 * gpsbabel DebianBug:816808
Line 83: Line 89:
 * kate4 DebianBug:816809
Line 84: Line 91:
 * kchmviewer DebianBug:784476 New upstream release available, can build against Qt5. Might need team uplod.  * kchmviewer DebianBug:784476 New upstream release available, can build against Qt5. Might need team upload.
Line 97: Line 104:
 * mediaconch DebianBug:816810
Line 108: Line 116:
 * pythonqt DebianBug:816811
Line 109: Line 118:
 * qutecom DebianBug:816812
Line 112: Line 122:
 * utopia-documents DebianBug:816813

Qt4's WebKit removal

Template text to file bugs

Subject: Qt4's WebKit removal
Source: @FILLME@
User: debian-qt-kde@lists.debian.org
Usertags: qt4webkit-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] <https://lists.debian.org/debian-devel-announce/2015/05/msg00001.html>

Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much upstreams
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library 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. In
order to ease the transition time we have provided Wheezy backports for Qt5.

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

Apps using Qt4's WebKit

Situation of apps and libraries using Qt4's ?WebKit

Reminder bugs filed against these packages

No reaction

WIP / bug upstream

Done