Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Fri, 24 Mar 2017, Ruben Undheim wrote: In some programs such as pcbnew (kicad), this is not just a simple Warning message being written to console, but actually an annoying message box popping up disturbing the work-flow. I honestly think this needs to be release-critical for Stretch. I requested a binNMU for wxpython. This should hopefully take care of it. Scott
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Tue, Feb 28, 2017 at 10:26:52PM -0500, Scott Talbert wrote: > Why was this binNMU done anyway? It seems to enable PIE (which is now the default with GCC6). Cheers, Olly
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Wed, 1 Mar 2017, Olly Betts wrote: But the release manager gets to override your artificially inflated severity so all that really achieves is to waste the RM's precious time. Why was this binNMU done anyway?
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Tue, Feb 28, 2017 at 08:37:39PM -0500, Scott Talbert wrote: > On Wed, 1 Mar 2017, Olly Betts wrote: > > >>It sure would be nice to get rid of this warning which will otherwise be > >>around for the duration of stretch. You don't think it's worth filing a > >>freeze exception? > > > >Severity "minor" means it doesn't meet the criteria: > > > >https://lists.debian.org/debian-devel-announce/2016/11/msg9.html > > True, but as I read the bug severity levels, it could be classified as > serious as a matter of maintainer opinion: "... or, in the package > maintainer's or release manager's opinion, makes the package unsuitable for > release." But the release manager gets to override your artificially inflated severity so all that really achieves is to waste the RM's precious time. Cheers, Olly
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Wed, 1 Mar 2017, Olly Betts wrote: This will have started because wxwidgets3.0 got binNMUed a few days ago. I doubt we can address this for stretch though. It sure would be nice to get rid of this warning which will otherwise be around for the duration of stretch. You don't think it's worth filing a freeze exception?
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Wed, 1 Mar 2017, Olly Betts wrote: It sure would be nice to get rid of this warning which will otherwise be around for the duration of stretch. You don't think it's worth filing a freeze exception? Severity "minor" means it doesn't meet the criteria: https://lists.debian.org/debian-devel-announce/2016/11/msg9.html True, but as I read the bug severity levels, it could be classified as serious as a matter of maintainer opinion: "... or, in the package maintainer's or release manager's opinion, makes the package unsuitable for release."
Bug#856341: [Freewx-maint] Bug#856341: python-wxgtk3.0: Warning about wxPython is using an older C++ ABI
On Tue, Feb 28, 2017 at 08:24:24PM -0500, Scott Talbert wrote: > On Wed, 1 Mar 2017, Olly Betts wrote: > >This will have started because wxwidgets3.0 got binNMUed a few days ago. > >I doubt we can address this for stretch though. > > It sure would be nice to get rid of this warning which will otherwise be > around for the duration of stretch. You don't think it's worth filing a > freeze exception? Severity "minor" means it doesn't meet the criteria: https://lists.debian.org/debian-devel-announce/2016/11/msg9.html Cheers, Olly
