Debian Bug report logs - #832420
ITP: qtwebengine -- Web content engine library for Qt

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sandro Knauß <bugs@sandroknauss.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ITP: qtwebengine -- Web content engine library for Qt

Date: Mon, 25 Jul 2016 12:56:36 +0200

Package: wnpp
Severity: wishlist
Owner: "Sandro Knauß" <bugs@sandroknauss.de>

* Package name    : qtwebengine
  Version         : 5.6.1
  Upstream Author : The Qt Company Ltd.
* URL             : http://trac.webengine.org/wiki/QtWebEngine
* License         : LGPL2+,GPL2+, BSD
  Programming Lang: C++
  Description     : Web content engine library for Qt

 QtWebEngine provides a Web browser engine that makes it easy to embed content
 from the World Wide Web into your Qt application.
 .
 This package contains the development files needed to build Qt 5 applications
 using QtWebEngine library.

We want to package it within the  Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> umrella
and need it for newer KDE Applications.

Message #12 received at 832420@bugs.debian.org (full text, mbox, reply):

From: Diederik de Haas <didi.debian@cknow.org>

To: 832420@bugs.debian.org

Subject: Re: Bug#832421: ITP: qtwebchannel -- Publish `QObjects` for the usage of webengine

Date: Mon, 25 Jul 2016 20:02:48 +0200

[Message part 1 (text/plain, inline)]

Control: block -1 by 832421

On maandag 25 juli 2016 13:04:20 CEST Sandro Knauß wrote:
> * Package name    : qtwebchannel
> It is needed for QtWebEngine.

Marking the QtWebEngine ITP as such

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 832420@bugs.debian.org (full text, mbox, reply):

From: Norbert Tretkowski <norbert@tretkowski.de>

To: "control@bugs.debian.org" <control@bugs.debian.org>, "832420@bugs.debian.org" <832420@bugs.debian.org>

Subject: unblock

Date: Fri, 29 Jul 2016 17:51:53 +0200

[Message part 1 (text/plain, inline)]

unblock 832159 with 832420
thanks

Hi,

qutebrowser works with either QtWebKit or QtWebEngine, so no reason to
block this.


Regards
Norbert

[signature.asc (application/pgp-signature, attachment)]

Message #34 received at 832420@bugs.debian.org (full text, mbox, reply):

From: Sandro Knauß <bugs@sandroknauss.de>

To: Debian Security Team <team@security.debian.org>

Cc: Debian Chromium Maintainers <pkg-chromium-maint@lists.alioth.debian.org>, 832420@bugs.debian.org

Subject: QtWebEngine ready for upload

Date: Mon, 31 Oct 2016 12:27:13 +0100

[Message part 1 (text/plain, inline)]

Hey,

I don't know if you heard about QtWebEngine - it is a Web browser engine for 
Qt applications. And is using a patched chromium (49.0.2623.111)( inside src/
3rdparty/chromium) as webengine. Qt itself depecated QWebKit and pushing 
everyone to use QWebEngine instead.
Unfortunately we didn't found a way to share parts with the chromium package :
( But this means, that security vulnerable that hit chromium may also affect 
QtWebEngine and the other way round.

For post Stretch we hopefully can find a solution to get rid of this copy...

Best Regards,

Sandro Knauß

[signature.asc (application/pgp-signature, inline)]

Message #41 received at 832420@bugs.debian.org (full text, mbox, reply):

From: Moritz Mühlenhoff <jmm@inutil.org>

To: Sandro Knauß <bugs@sandroknauss.de>

Cc: Debian Security Team <team@security.debian.org>, Debian Chromium Maintainers <pkg-chromium-maint@lists.alioth.debian.org>, 832420@bugs.debian.org

Subject: Re: QtWebEngine ready for upload

Date: Fri, 11 Nov 2016 18:46:34 +0100

On Mon, Oct 31, 2016 at 12:27:13PM +0100, Sandro Knauß wrote:
> Hey,
> 
> I don't know if you heard about QtWebEngine - it is a Web browser engine for 
> Qt applications. And is using a patched chromium (49.0.2623.111)( inside src/
> 3rdparty/chromium) as webengine. Qt itself depecated QWebKit and pushing 
> everyone to use QWebEngine instead.
> Unfortunately we didn't found a way to share parts with the chromium package :
> ( But this means, that security vulnerable that hit chromium may also affect 
> QtWebEngine and the other way round.
> 
> For post Stretch we hopefully can find a solution to get rid of this copy...

Hi,
I don't think we're realistically be able to cover that with security support
(and QT upstream won't be able either): chromium is a highly volatile target
and the only way we're able to support it is by following their upstream releases,
which makes aggressive changes over time.

So QWebEngine in stretch will be as unsupported as as in QWebkit was in jessie:
https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#browser-security

Cheers,
        Moritz

Message #46 received at 832420-done@bugs.debian.org (full text, mbox, reply):

From: Felix Gruber <felgru@gmx.de>

To: 832420-done@bugs.debian.org

Subject: QTWebEngine is now in stretch

Date: Mon, 9 Jan 2017 00:19:35 +0100

Closing this ITP as QTWebEngine is now available in stretch under the
name libqt5webengine5.

Cheers,
Felix

Send a report that this bug log contains spam.