[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#844526: marked as done (nmu: wxwidgets3.0_3.0.2+dfsg-2)

Your message dated Thu, 17 Nov 2016 15:37:13 +0200
with message-id <20161117133713.numw5w4yakbi6cda@bunk.spdns.de>
and subject line Re: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt
has caused the Debian Bug report #844526,
regarding nmu: wxwidgets3.0_3.0.2+dfsg-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
844526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844526
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu


Dear release team,

wxwidgets needs to be recompiled due to a versions mismatch.
See #844486 for more details.

Recompiling this package fixes the problem in #844486

nmu wxwidgets3.0_3.0.2+dfsg-2 . ANY . unstable . -m "Fix ABI mismatch"


Thanks,

Anton

--- End Message ---
--- Begin Message --- 
Control: reassign -1 src:wxwidgets3.0
Control: retitle -1 wxwidgets3.0 should drop the ABI mismatch message
Control: affects -1 gnuplot-qt

On Thu, Nov 17, 2016 at 09:41:07AM +0100, Vincent Lefevre wrote:
> On 2016-11-17 14:36:08 +1300, Olly Betts wrote:
> > In upstream wxWidgets, if the compile-time ABI and run-time ABI don't
> > match, then you get an error and the app won't run, which is just not
> > helpful.  In Debian we reduce that error to a warning - in practice I've
> > never seen an actual problem due to this, but leaving the warning there
> > means that this at least gets flagged as a potential issue.
> 
> A warning can be very annoying (e.g. because it mixes with other output
> to the terminal) and possibly break scripts that don't expect output to
> stderr. If this is not expected to work, then an error like upstreams's
> behavior is the right thing to do (there is a real issue, and the user
> must make sure that it gets fixed). Otherwise a warning isn't needed,
> except in some debug mode for developers or andvanced users (but such
> a mode would not be the default).

Yes, this is what should be done.

When the C++ ABI changes in an incompatible way (like it did a year ago),
there will anyway be a complete ABI transition in Debian - any
potential issue would not be specific to wxWidgets.

Matthias Klose confirmed that ABI version 10 is supposed to be backwards 
compatible with ABI version 9.

I'm closing the binNMU request and move the other bug
to src:wxwidgets3.0

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--- End Message ---
Reply to: