Your message dated Sun, 06 Aug 2017 04:45:41 +0000
with message-id <e1dedrd-0001vw...@fasolo.debian.org>
and subject line Bug#869366: Removed package(s) from unstable
has caused the Debian Bug report #784619,
regarding [creepy] 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.)
--
784619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: creepy
Severity: wishlist
User: debian-qt-...@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]. Your package seems to be using it via PyQt4's
QtWebKit module.
[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 upstream
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/PyQt5 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] and the
PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting
your application.
[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
[pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html
For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org.
--
Dmitry Shachnev,
on behalf of the Qt4 and PyQt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.4.1-5+rm
Dear submitter,
as the package creepy has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/869366
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
