Your message dated Sun, 17 Dec 2017 13:37:12 +0300
with message-id <20171217103712.gb3...@mitya57.me>
and subject line Re: Bug#879958: python3-pyqt5.qtwebengine: package not
available for Raspberry Pi
has caused the Debian Bug report #879958,
regarding python3-pyqt5.qtwebengine: package not available for Raspberry Pi
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.)
--
879958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
-- System Information:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.1 (stretch)
Release: 9.1
Codename: stretch
Architecture: armv6l
Kernel: Linux 4.9.41+
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Peter, and thanks for your response!
On Sun, Dec 17, 2017 at 02:39:56AM +0000, peter green wrote:
> 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.
Qt WebEngine supports armv6. To detect the architecture to build for, it
parses the compiler logs and looks for -march=armvX option.
I suggest you to check this code:
http://code.qt.io/cgit/qt/qtwebengine.git/tree/src/core/config/linux.pri#n46
Though there can be third-party code in Chromium that does not use the
standard build system, and it may be broken with armv6. If that is the case,
please file a bug upstream.
I am now closing this bug, as pyqt5 WebEngine support cannot be provided
for Raspbian until there is WebEngine itself.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
