Bug#784612: [anki] Qt4's WebKit removal
On Mon, Jan 23, 2017 at 10:48:53PM +0100, Nicolas Kuttler wrote: > On 2017-01-23 21:40, Julian Gilbey wrote: > > On Wed, Jul 13, 2016 at 07:08:23AM +0200, Nicolas Kuttler wrote: > > > There are alpha builds with Qt5 available, > > > > > > http://ankisrs.net/download/mirror/alpha/ > > > > > > https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1 > > > > > > https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2 > > > > I have managed to create a working Debian package based on the latest > > alpha. Would you like me to send the changes to the collab-maint > > repository? > > I'm not an Anki dev, just a user, I don't know about their repositories. > As a Debian user, at the moment I'd rather see Anki removed from Debian. > It doesn't look like we'll have a usable release before the stretch > freeze, but by all means, contribute your code upstream. I hope a stable > Qt5 Anki will appear in backports rather sooner than later. Hi Nicolas, This was a comment on the Debian bug report; I'm suggesting uploading my changes to the Debian anki collab-maint repository. It's too late for anki to get into stretch, as we are now in quite deep freeze, and it has been removed from testing. But the version I have created, especially when 2.1.0 has stabilised, should be able to be backported to backports. In the meantime, it can be uploaded to unstable (at least once my new package, python3-send2trash, which is needed by anki 2.1.0, has been processed through the NEW queue; this can also easily be backported to stretch-backports). Best wishes, Julian
Bug#784612: [anki] Qt4's WebKit removal
On 2017-01-23 21:40, Julian Gilbey wrote: > On Wed, Jul 13, 2016 at 07:08:23AM +0200, Nicolas Kuttler wrote: > > There are alpha builds with Qt5 available, > > > > http://ankisrs.net/download/mirror/alpha/ > > > > https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1 > > > > https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2 > > I have managed to create a working Debian package based on the latest > alpha. Would you like me to send the changes to the collab-maint > repository? I'm not an Anki dev, just a user, I don't know about their repositories. As a Debian user, at the moment I'd rather see Anki removed from Debian. It doesn't look like we'll have a usable release before the stretch freeze, but by all means, contribute your code upstream. I hope a stable Qt5 Anki will appear in backports rather sooner than later.
Bug#784612: [anki] Qt4's WebKit removal
On Wed, Jul 13, 2016 at 07:08:23AM +0200, Nicolas Kuttler wrote: > There are alpha builds with Qt5 available, > > http://ankisrs.net/download/mirror/alpha/ > > https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1 > > https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2 I have managed to create a working Debian package based on the latest alpha. Would you like me to send the changes to the collab-maint repository? Best wishes, Julian
Bug#784612: [anki] Qt4's WebKit removal
There are alpha builds with Qt5 available, http://ankisrs.net/download/mirror/alpha/ https://anki.tenderapp.com/discussions/beta-testing/172-anki-210-alpha-1 https://anki.tenderapp.com/discussions/beta-testing/174-anki-210-alpha-2
Bug#784612: [anki] Qt4's WebKit removal
Hi, I'm posting a modified version of Richard's Dockerfile for people using fcitx and Chinese. I know nothing about docker but the configuration appears to be running and can be used as the starting point for others. https://gist.github.com/ondrik/95850021e9046483df91c46d9a23ad2b Best, Ondra -- Ondrej Lengal(龍安卓) GPG: 40FD 3AE9 0BFA B151 4358 6194 5792 8315 149F 91C8 signature.asc Description: PGP signature
Bug#784612: [anki] Qt4's WebKit removal
On Fri, 3 Jun 2016 03:01:06 +0200 Andreas Bombewrote: […] > Right, until there's a Qt5 port, little can be done. I have actually […] This is not a good solution for everyone, but I'm now running Anki inside a Debian Jessie Docker container. See here for how to do it: http://cloj.de/AnkiDocker/ Best, Richard signature.asc Description: PGP signature
Bug#784612: [anki] Qt4's WebKit removal
On 2016-06-03 03:01, Andreas Bombe wrote: > On Mon, May 30, 2016 at 02:42:19AM +0200, Nicolas Kuttler wrote: > > For anybody else wondering about this, the maintainer has already > > contacted upstream and they are aware of the problem, > > https://anki.tenderapp.com/discussions/ankidesktop/16516 > > Right, until there's a Qt5 port, little can be done. I have actually > experimentally ported it a while ago and ran into a few significant > problems. I need to update my code to the latest upstream git and submit > it for consideration. There is another Qt5 repository at https://github.com/intact/anki/, it has the same issues you mentioned. After removing my conflicting plugins and creating a new profile I was able to use it.
Bug#784612: [anki] Qt4's WebKit removal
On Mon, May 30, 2016 at 02:42:19AM +0200, Nicolas Kuttler wrote: > For anybody else wondering about this, the maintainer has already > contacted upstream and they are aware of the problem, > https://anki.tenderapp.com/discussions/ankidesktop/16516 Right, until there's a Qt5 port, little can be done. I have actually experimentally ported it a while ago and ran into a few significant problems. I need to update my code to the latest upstream git and submit it for consideration. The significant problems are that it has plugins and Qt4/Qt5 don't work together in the same program. The other big problem is that the configuration is a serialized dump of some Python data and some Qt4 package name is encoded in it. Loading old configuration in the Qt5 port will make it crash. So yeah, even if I submit my port ASAP there are still some showstoppers to iron out.
Bug#784612: [anki] Qt4's WebKit removal
For anybody else wondering about this, the maintainer has already contacted upstream and they are aware of the problem, https://anki.tenderapp.com/discussions/ankidesktop/16516
Bug#784612: [anki] Qt4's WebKit removal
Package: anki Version: 2.0.32+dfsg-1 Followup-For: Bug #784612 Control: severity -1 grave Dear Maintainer, as said in the last response, anki is not usable at all anymore. Raising the severity to grave. This has severe impact on people, please at least respond so that we know what to expect (or not) and when. Thanks for your work, -- Rémi -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages anki depends on: ii libjs-jquery 1.12.3-1 ii libjs-jquery-flot 0.8.3+dfsg-1 ii libjs-jquery-ui 1.10.1+dfsg-1 ii python2.7.11-1 ii python-beautifulsoup 3.2.1-1 ii python-httplib2 0.9.1+dfsg-1 ii python-pyaudio0.2.8-1+b3 ii python-qt44.11.4+dfsg-2 ii python-simplejson 3.8.2-2 ii python-sqlalchemy 1.0.12+ds1-1 pn python:any Versions of packages anki recommends: ii python-matplotlib 1.5.1-1+b2 Versions of packages anki suggests: pn dvipng ii lame 3.99.5+repack1-9+b1 pn mplayer2 -- no debconf information
Bug#784612: [anki] Qt4's WebKit removal
Package: anki Version: 2.0.32+dfsg-1 Followup-For: Bug #784612 Dear Maintainer, it seems like anki is not usable any more. I guess this was expected but I'm wondering if there is a plan for the future. Severity should probably be bumped to grave. $ anki Traceback (most recent call last): File "/usr/bin/anki", line 7, in import aqt File "/usr/share/anki/aqt/__init__.py", line 12, in from aqt.qt import * File "/usr/share/anki/aqt/qt.py", line 22, in from PyQt4.QtWebKit import QWebPage, QWebView, QWebSettings ImportError: No module named QtWebKit -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages anki depends on: ii libjs-jquery 1.12.3-1 ii libjs-jquery-flot 0.8.3+dfsg-1 ii libjs-jquery-ui 1.10.1+dfsg-1 ii python2.7.11-1 ii python-beautifulsoup 3.2.1-1 ii python-httplib2 0.9.1+dfsg-1 ii python-pyaudio0.2.8-1+b3 ii python-qt44.11.4+dfsg-2 ii python-simplejson 3.8.2-2 ii python-sqlalchemy 1.0.12+ds1-1 pn python:any Versions of packages anki recommends: ii python-matplotlib 1.5.1-1+b2 Versions of packages anki suggests: pn dvipng ii lame 3.99.5+repack1-9+b1 pn mplayer2 -- no debconf information
Bug#784612: [anki] Qt4's WebKit removal
Source: anki Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4webkit-removal Control: block 784513 by -1 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/msg1.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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org