On Mon, Sep 16, 2019 at 09:25:54AM -0400, Scott Talbert wrote: > On Mon, 16 Sep 2019, Gunter Königsmann wrote: > > That only partially answers my question. Currently I am playing with the > > thought if the right idea would be uploading a wxMaxima version that > > uses GTK3 to debian testing and looking if anyone except Vadim and me is > > affected by the bug.
Note you don't upload to testing - you upload to unstable, and then the package migrates to testing. I think this is probably a good idea. It seems there's something system dependent here since wxmaxima rebuilt to use GTK3 doesn't seem to flicker when scrolling horizontally or vertically to me, and so allowing easy wider testing would be helpful in trying to work out what's going on. > Well, the only thing we can control is that the GTK2 build of wx will be > gone in Bullseye, barring any unforseen circumstances. Whether that will be > with wx 3.0 or wx 3.2, remains to be seen. At this point the wxwidgets3.0-gtk3 transition is reporting 54% done: https://release.debian.org/transitions/ There's also one bug tagged "pending" and two packages uploaded to "experimental", so effectively 57% if you include stuff that's in progress (there are about 100 packages involved in all). I think even if wx 3.2 does come out soon we'd really want to get the current transition completed first. Having to deal with 3 wx variants at once sounds like more pain than necessary, and if we get the GTK2->GTK3 issues dealt with now then that's less to deal with in the second transition. Cheers, Olly
