Your message dated Thu, 4 Dec 2014 00:35:48 +0000
with message-id <[email protected]>
and subject line Re: Bug#766790: fixed in erlang 1:17.3-dfsg-3
has caused the Debian Bug report #766790,
regarding wxwidgets3.0: ABI break: constants wxLANGUAGE_KOREAN and after
renumbered
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 [email protected]
immediately.)
--
766790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766790
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: wxwidgets3.0
Version: 3.0.1-1
Severity: normal
In the upstream 3.0.1 release, wxLANGUAGE_KABYLE was added by inserting it
into the sorted list of language names just before wxLANGUAGE_KOREAN -
the developer who made this change didn't spot that this breaks applications
using such constants if built against 3.0.0 and using a later version of wx.
I've not seen any actual reports of problems, but the likely consequence
is that the wrong language would get selected, which would be pretty
annoying for users to have to work around.
A quick poke in codesearch.d.n suggests that only a small subset of
wx-using applications actually make use of these constants, so I propose
to work out which applications might be affected and check the version of
wx they were built against to produce a list to be binNMU-ed.
Cheers,
Olly
--- End Message ---
--- Begin Message ---
On Wed, Dec 03, 2014 at 12:49:16PM +0100, Ivo De Decker wrote:
> On Sun, Nov 30, 2014 at 09:21:06PM +0000, Sergei Golovan wrote:
> > Source: erlang
> > Source-Version: 1:17.3-dfsg-3
>
> > * Added a patch by Olly Betts which updates hard-coded wx constant values
> > for wx3.0 (closes: #766790).
>
> This is actually bug 770892. I closed that one and reopened this one.
Sorry, this confusion is likely my fault, as I mentioned #766790 in the
patch I provided.
And in fact now #770892 is fixed and the upload unblocked, we can close
#766790 too. I've double checked the list of packages which might be
affected, and they're all dealt with now.
Cheers,
Olly
--- End Message ---
