Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-26 Thread Olly Betts
On Tue, Sep 26, 2017 at 08:24:06AM -0400, Scott Talbert wrote:
> 
> 
> On September 26, 2017 1:54:34 AM EDT, Olly Betts  wrote:
> >On Mon, Sep 25, 2017 at 10:37:34PM -0400, Scott Talbert wrote:
> >> I would think the person who was trying to use wx.html2 might not
> >> agree with that.
> >
> >"wx.html2" is actually how wxPython wraps webview:
> >
> >| I have put the wxPython verison of them in the wx.html2 module
> >| because the wxWebKit project already produces a wx.webview module for
> >| wxPython.
> >
> >So it's inevitable that wx.html2 is not going to work once webview is
> >disabled in wxWidgets.
> 
> I am fully aware of that.  I just think it would have been better to
> leave it until wxWebview was being removed.

That's imminent anyway.

And the original reporter of #821934 wasn't even using Debian!

Cheers,
Olly



Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-26 Thread Scott Talbert


On September 26, 2017 1:54:34 AM EDT, Olly Betts  wrote:
>On Mon, Sep 25, 2017 at 10:37:34PM -0400, Scott Talbert wrote:
>> On Tue, 26 Sep 2017, Olly Betts wrote:
>> >If we revert the change which added this package apart from one hunk
>in
>> >debian/rules then we get a package set which simply doesn't have
>> >wx.html2 (rather than a broken one), which seems good so I've
>uploaded.
>> 
>> I would think the person who was trying to use wx.html2 might not
>agree with
>> that.
>
>"wx.html2" is actually how wxPython wraps webview:
>
>| I have put the wxPython verison of them in the wx.html2 module
>| because the wxWebKit project already produces a wx.webview module for
>| wxPython.
>
>So it's inevitable that wx.html2 is not going to work once webview is
>disabled in wxWidgets.

I am fully aware of that.  I just think it would have been better to leave it 
until wxWebview was being removed.



Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-25 Thread Olly Betts
On Mon, Sep 25, 2017 at 10:37:34PM -0400, Scott Talbert wrote:
> On Tue, 26 Sep 2017, Olly Betts wrote:
> >If we revert the change which added this package apart from one hunk in
> >debian/rules then we get a package set which simply doesn't have
> >wx.html2 (rather than a broken one), which seems good so I've uploaded.
> 
> I would think the person who was trying to use wx.html2 might not agree with
> that.

"wx.html2" is actually how wxPython wraps webview:

| I have put the wxPython verison of them in the wx.html2 module
| because the wxWebKit project already produces a wx.webview module for
| wxPython.

So it's inevitable that wx.html2 is not going to work once webview is
disabled in wxWidgets.

Cheers,
Olly



Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-25 Thread Scott Talbert

On Tue, 26 Sep 2017, Olly Betts wrote:


On Tue, 26 Sep 2017, Olly Betts wrote:

So it might not actually be as easy as you might think to disable
webview here before we disable it in wxwidgets3.0...

I'll kick off a build and see.  If it doesn't just work, I'm inclined
to disable this at the same time as we do wxwidgets3.0.


If we revert the change which added this package apart from one hunk in
debian/rules then we get a package set which simply doesn't have
wx.html2 (rather than a broken one), which seems good so I've uploaded.


I would think the person who was trying to use wx.html2 might not agree 
with that.



Yeah, I would say we should just do this when wxwidgets3.0 loses its webkit1
dependency (or preferably this problem just goes away when switching
wxwidgets to GTK+ 3).


I wouldn't rely on a switch to GTK+ 3 happening for buster - I did a bit
of work towards it, and upstream are responsive to reports of bugs under
GTK+ 3 (at least when they can reproduce them) but unfortunately I don't
really have the time to drive this forwards currently, and nobody else
seems to be actively working on it.


:(



Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-25 Thread Olly Betts
On Mon, Sep 25, 2017 at 08:54:16PM -0400, Scott Talbert wrote:
> On Tue, 26 Sep 2017, Olly Betts wrote:
> >So it might not actually be as easy as you might think to disable
> >webview here before we disable it in wxwidgets3.0...
> >
> >I'll kick off a build and see.  If it doesn't just work, I'm inclined
> >to disable this at the same time as we do wxwidgets3.0.

If we revert the change which added this package apart from one hunk in
debian/rules then we get a package set which simply doesn't have
wx.html2 (rather than a broken one), which seems good so I've uploaded.

> Yeah, I would say we should just do this when wxwidgets3.0 loses its webkit1
> dependency (or preferably this problem just goes away when switching
> wxwidgets to GTK+ 3).

I wouldn't rely on a switch to GTK+ 3 happening for buster - I did a bit
of work towards it, and upstream are responsive to reports of bugs under
GTK+ 3 (at least when they can reproduce them) but unfortunately I don't
really have the time to drive this forwards currently, and nobody else
seems to be actively working on it.

Cheers,
Olly



Bug#876789: [Freewx-maint] Bug#876789: python-wxgtk-webview3.0: Depends on libwxgtk-webview3.0-0v5 which depends on webkit1

2017-09-25 Thread Scott Talbert

On Tue, 26 Sep 2017, Olly Betts wrote:


Looks like this package was partly enabled to fix a problem with the
build without it:

https://bugs.debian.org/821934

So it might not actually be as easy as you might think to disable
webview here before we disable it in wxwidgets3.0...

I'll kick off a build and see.  If it doesn't just work, I'm inclined
to disable this at the same time as we do wxwidgets3.0.


Yeah, I would say we should just do this when wxwidgets3.0 loses its 
webkit1 dependency (or preferably this problem just goes away when 
switching wxwidgets to GTK+ 3).


Scott