On 16/12/17 16:10, Dmitry Shachnev wrote:
Control: tags -1 moreinfo
Hi, and sorry for the delay!
On Fri, Oct 27, 2017 at 06:41:31PM +0200, activityworkshop wrote:
Package: python3-pyqt5.qtwebengine
Severity: important
Dear Maintainer,
According to packages.debian.org, this package is only built for amd64 and
i386 architectures.
To use it on the Raspberry Pi, one would need it to be built also for ARM.
The Qt5 packages on which this one depends, such as libqt5qui5,
libqt5webenginecore5, libqt5webenginewidgets5 etc, already appear to be
built.
Is this just an oversight, that the python bindings are missing?
As an aside, Raspbian already includes architecture-neutral packages which
depend on this python3-pyqt5.qtwebengine package, and these fail to install.
In fact I think this bug report should go to Raspbian, not to Debian.
>From the Raspbian build logs [1], it looks like qtwebengine is available
there only in buster, not in stretch (even though the version from Debian
stretch builds fine on armhf).
Also for some reason even when I added qtwebengine/armhf support to pyqt5 in
5.7+dfsg-6, the Raspbian developers reverted that change in 5.7+dfsg-6+rpi1
upload (and it is still reverted in 5.9+dfsg-2+rpi1 [2]):
* Disable webengine for armhf, we do not currently have (and may never have)
it in Raspbian.
-- Peter Michael Green <plugw...@raspbian.org> Sat, 09 Sep 2017 01:01:09
+0000
I do not know the reasoning for that change, so adding Peter to CC in hope
he can explain it.
Hi.
qtwebengine built sucessfully but failed to pass the armv7 contamination check,
so was not uploaded. The combination of hellishly long build times, massively
complicated build systems (chromiums build system embedded in qt) which i'm
unfamiliar with and the fact that I have little idea how to properly test
qtwebengine put further detailed investigation of this beyond what I can
reasonablly do.
If someone can fix it so it doesn't show armv7 contamination and/or they can
show that any (remaining) armv7 contamination is a false positive (i.e. it is
gaurded behind runtime checks) then we can work to get a qtwebengine package in
Raspbian.
The raspberry pi foundation have a chromium package but again I don't have the
expertise to turn it into something suitable for Raspbian proper (i.e. no
dependencies on raspberry pi foundation libraries. I also don't know how
similar the plain chromium source is to the embedded chromium in qtwebengine.
