Your message dated Thu, 11 Aug 2016 23:25:23 +0200 with message-id <6932812.te2j3lp9UP@pendragon> and subject line Fixed with digikam 5.0 has caused the Debian Bug report #784460, regarding [digikam] Qt4's WebKit removal to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 784460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: digikam Version: 4:4.4.0-1.1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Dear Debian KDE Extras Team <firstname.lastname@example.org>, 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 latest Qt4 point release and upstream is migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream support for maintaining Qt4's WebKit. 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/packagingqtstuff.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-...@lists.debian.org Ana, on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---Source: digikam Source-Version: 4:5.0.0-1 Hi, since version 5.0, digikam is ported to Qt5 and KDE Frameworks, and thus Qt4's WebKit is no more used. Thanks, -- Pino Toscano
Description: This is a digitally signed message part.
--- End Message ---