<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-07-31 7:16 GMT+02:00 Olly Betts <span dir="ltr"><<a href="mailto:olly@survex.com" target="_blank">olly@survex.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 6 July 2017 at 08:49, Björn Harrtell <<a href="mailto:bjorn.harrtell@gmail.com">bjorn.harrtell@gmail.com</a>> wrote:<br>
> 2017-07-05 1:38 GMT+02:00 Olly Betts <<a href="mailto:olly@survex.com">olly@survex.com</a>>:<br>
>> Björn Harrtell <<a href="mailto:bjorn.harrtell@gmail.com">bjorn.harrtell@gmail.com</a>> wrote:<br>
>> > I'm wondering if there are any plans to package wxWidgets 3.0/3.1<br>
>> > compiled for GTK+ 3?<br>
>><br>
>> It's not feasible to package wxWidgets 3.1, as it doesn't have a stable<br>
>> ABI - each new upstream version would potentially require a library<br>
>> transition in Debian.<br>
>><br>
>> I had been hoping to switch to GTK3 with wx 3.2, but currently it looks<br>
>> unlikely to me that upstream will release 3.2 soon, or at least soon<br>
>> enough for it to be feasible to switch to for buster (we probably have<br>
>> about 16 months before the buster freeze. The 2.8 to 3.0 transition<br>
>> took around a year, though there were quite a lot of incompatibilities<br>
>> to deal with - I'd hope 3.0 to 3.2 is smoother, but even so with the<br>
>> number of reverse dependencies wx has in Debian, a transition will take<br>
>> time).<br>
<br>
</span>After discussions with wx upstream, they seem keen to try to get 3.2 out sooner.<br>
<br>
3.0 to 3.2 API changes are small, though by default 3.2 drops<br>
compatibility for the large amount of stuff removed/changed between<br>
2.8 and 3.0. But wx upstream suggested Debian shipping 3.2 with 2.8<br>
compatibility enabled would be better than shipping 3.0. If they're<br>
happy with that, I'm happier shipping such a configuration.<br>
<br>
However, wxPython "classic" seem like it's probably seen its last<br>
release, and migrating rdeps to wxPython "phoenix" seems like it<br>
requires quite a lot of code changes, which means more work for a<br>
transition until enough time has passed for upstreams of projects<br>
using it to have done the necessary changes. But wxPython "phoenix"<br>
has only just made its first beta release, so we can't expect many<br>
upstreams to have migrated in time for buster.<br>
<br>
I really don't have the time or energy for a wxPython transition which<br>
is going to require a lot of cajoling of maintainers and upstreams, so<br>
unless there's someone who does I think we may have to stick with wx<br>
3.0 for buster. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>> The first thing we need to determine is whether the GTK version used<br>
>> affects the ABI of the built libraries, so that would be useful to<br>
>> check.<br>
<br>
</span>Actually the gtk2/gtk3 choice is encoded in the library name, so ABI<br>
compatibility isn't relevant as we really need to handle this as an<br>
ABI change anyway.<br>
<br>
E.g. here's 3.0 built with GTK2 and 3.1 built with GTK3:<br>
<br>
<a href="http://libwx_gtk2u_core-3.0.so" rel="noreferrer" target="_blank">libwx_gtk2u_core-3.0.so</a><br>
<a href="http://libwx_gtk3u_core-3.1.so" rel="noreferrer" target="_blank">libwx_gtk3u_core-3.1.so</a><br>
<span class=""><br>
> If 3.2 is way off, perhaps it can still be worth switching to GTK 3 for<br>
> wxWidgets 3.0.<br>
<br>
</span>I've now uploaded 3.0.3.1 (built with GTK2) which is due to migrate to<br>
testing in the next day or so, so we're at least up to date with<br>
upstream releases.<br>
<br>
I'm looking at a build of this using GTK3 to upload to experimental or<br>
maybe unstable (if it's easy to make the packages parallel install<br>
cleanly). That'll at least allow rdeps to easily test compatibility<br>
with such a build.<br>
<span class=""><br>
> FWIW my personal interest in this is to extend the life of<br>
> pgadmin3.<br>
<br>
</span>Does debian's wx packages switching to GTK3 help there?<br>
<a href="https://www.pgadmin.org/download/" rel="noreferrer" target="_blank">https://www.pgadmin.org/<wbr>download/</a> says:<br>
<br>
| WARNING: pgAdmin 3 is no longer supported.<br>
<br>
So I'd expect a switch to GTK3 to if anything be bad for Debian's<br>
pgadmin3 package, as any issues which are actually in the pgadmin3<br>
code won't get solved by pgadmin upstrream.<br></blockquote><div><br></div><div>I know pgadmin3 is abandoned since quite some time now but some people including me would like to see it continued as pgadmin4 isn't a good replacement in our view at this time. I'm trying to find a way to gather enough interest and people to convince the old maintainer(s) to transfer it us, but it needs a certain level of seriousness to be sure.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> However, I'm not confident about the stability of wxWidgets 3.0<br>
> with GTK 3 at this time<br>
<br>
</span>My own testing of a build with GTK3 uncovered some issues. It seems<br>
wx upstream are responsive to GTK3-related bugs, and they've fixed<br>
those they can reproduce.<br>
<br>
However, at least one problem I found they can't reproduce.<br></blockquote><div><br></div><div>If wx 3.0 and GTK3 is the likely way ahead for buster I'll be glad to investigate that road for pgadmin3. I already have some WIP patches for that but the maintenance situation needs resolving for it to have value I guess.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
Olly<br>
</blockquote></div><br></div></div>