On Thu, 17 Apr 2025, Paul Gevers wrote:
Hi Scott, [Next time, please file an unblock bug against release.debian.org]
My bad, I didn't know that was the process.
On 17-04-2025 16:12, Scott Talbert wrote:Any chance you could push wxpython4.0 4.2.3+dfsg-2 to testing sooner than 5 days from now? The version in testing right now is completely broken and is resulting in RC bugs piling up.Can you elaborate? I read from https://bugs.debian.org/1102946#21 """ This was due to an unfortunate ABI version script change upstream in wxWidgets, fixed by the newer upload of wxPython. """What does that mean? 4.2.2 seems to be around for a while already and 4.2.3 hasn't reached testing yet.
Yes, so the bug was technically introduced by the wxwidgets3.2 3.2.7+dfsg-1 update - wxWidgets upstream made an error in the version script which resulting in 3.2.7 being ABI-incompatible with 3.2.6, although it was supposed to be. I unfortunately didn't notice this until wxwidgets3.2 3.2.7+dfsg-1 had already migrated to testing. (Note to self: adding autopkgtests to wxpython4.0 would be a good idea!)
So, it isn't the wxpython4.0 new release that fixes the issue, but rather just rebuilding wxpython4.0 with the unfortunately wxwidgets3.2 change.
Thanks, Scott