Dear Ana,

thank you for the bug report.

I fear that qupzilla depends no longer from Qt4. The version available
in Stretch is 1.8.6~dfsg1-2 ; here are a few tests:

$ dpkg -l qupzilla| grep ii
ii  qupzilla       1.8.6~dfsg1-2 amd64        lightweight web browser based on 
libqtwebkit
$ ldd $(which qupzilla)| grep -i qt
        libQt5WebKitWidgets.so.5 => 
/usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5 (0x00007f04a9b8a000)
        libQt5PrintSupport.so.5 => 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 (0x00007f04a9919000)
        libQt5WebKit.so.5 => /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 
(0x00007f04a7308000)
        libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 
(0x00007f04a6ab3000)
        libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 
(0x00007f04a6830000)
        libQt5Script.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 
(0x00007f04a63a3000)
        libQt5Sql.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5 
(0x00007f04a6161000)
        libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 
(0x00007f04a5e03000)
        libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 
(0x00007f04a56cd000)
        libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 
(0x00007f04a4f91000)
        libQt5OpenGL.so.5 => /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5 
(0x00007f04a34f0000)
        libQt5Quick.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 
(0x00007f049fd17000)
        libQt5Qml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 
(0x00007f049f6fa000)


May I close the bugreport?

Best regards,                   Georges.

Ana Guerrero Lopez a écrit :
> Source: qupzilla
> Version: 1.8.6~dfsg1-2
> Severity: wishlist
> User: [email protected]
> Usertags: qt4webkit-removal
> 
> Dear Georges Khaznadar <[email protected]>,
> 
> 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 [email protected]
> 
> Ana,
> on behalf of the Qt4 maintainers
> 

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70

Attachment: signature.asc
Description: Digital signature

Reply via email to