Control: tags -1 + moreinfo On Fri, 2017-03-24 at 20:34 -0400, Scott Talbert wrote: > wxwidgets3.0 was recently binNMU'd in stretch. wxpython3.0 needs to be > rebuilt to avoid a C++ ABI mismatch warning when all wxPython > applications are used.
It was binNMUed _in unstable_, a month ago. If there's an issue, why wasn't it noticed earlier? More specifically, I can only see one binNMU for wxpython3.0 having been performed in the past, in 2015. If the packages are so tightly coupled, shouldn't there have been far more frequent rebuilds in the past? (and how did the combination of wxwidgets3.0 uploaded on 2016-07-29 and wxpython3.0 uploaded on 2016-07-19 work?) > nmu wxpython3.0_3.0.2.0+dfsg-3 . ANY . stretch . -m "Rebuild due to wxWidgets > C++ ABI change" That won't work, in any case - unstable and testing have the same binary version of the packages, so the binNMUs would have to be performed in unstable and then migrate (as testing can't have a higher version of the package than unstable). Regards, Adam
