On 12.06.2014 07:23, Olly Betts wrote: [...] > We're aiming to migrate the archive to using wxwidgets3.0 instead of > wxwidgets2.8, and intend to drop wxwidgets2.8 before jessie is released.
Hi Olly, back then I was not sure if the wxwidgets3.0 transition is really going to happen before the freeze. > I had springlobby down on the list of packages that were already using > wxwidgets3.0, but I just spotted that in the latest upload you've switched > springlobby from back to wxwidgets2.8. That's working against the > on-going wxwidgets3.0 transition: > > https://release.debian.org/transitions/html/wxwidgets3.0.html > > What were the problems that using wxwidgets3.0 was causing? I don't see > anything about this in the BTS, and the changelog entry doesn't mention > anything specific. The main reason for switching back is that springlobby is buggy with wxwidgets3.0 and upstream states that: "wx 3.0 is currently badly supported / not tested. if possible use wx 2.8" [1] You can easily verify this by compiling springlobby with wxwidgets3.0. Then start the application and go to Edit->Preferences. The result is an assertion which I had reported upstream. https://github.com/springlobby/springlobby/issues/235 There are more issues https://github.com/springlobby/springlobby/issues/234 > At this point in the transition (and in the jessie release cycle), I'd > definitely recommend that packages stick with wxwidgets3.0 and we work > on resolving any issues. That way there's a good chance to actually > resolve them before the jessie freeze. I am not sure if we can do a better job than upstream here but I am open for any suggestions. Regards, Markus [1] https://github.com/springlobby/springlobby/issues/235
signature.asc
Description: OpenPGP digital signature