Your message dated Mon, 11 Jul 2022 12:10:54 +1200
with message-id <Ystqji7S2+/[email protected]>
and subject line Re: Bug#877181: libwxgtk3.0-0v5: wxExecute fails with
non-ascii characters
has caused the Debian Bug report #877181,
regarding libwxgtk3.0-0v5: wxExecute fails with non-ascii characters
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.)
--
877181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877181
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libwxgtk3.0-0v5
Version: 3.0.2+dfsg-4
Severity: normal
Tags: patch
Dear Maintainer,
wxWidgets has a known bug which prevents wxExecute for correctly handling
arguments with non-ascii characters. The bug was discussed and reported in
http://trac.wxwidgets.org/ticket/16206
Upstream fixed the issue in the development version (wxWidgets-3.1).
The bug affects all the programs relyig on wxExecute functionality, for example
`hugin` (see https://groups.google.com/forum/#!topic/hugin-ptx/FCi7ykPDZ5E).
The fix is a simple one-line patch
(https://github.com/wxWidgets/wxWidgets/commit/704055f200d97f327a8ee5212762b41bf1d6d503)
which works for the current version (3.0.3.1) as well.
Thanks,
Guy
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libwxgtk3.0-0v5 depends on:
ii libc6 2.24-11+deb9u1
ii libcairo2 1.14.8-1
ii libgcc1 1:6.3.0-18
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u1
ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2
ii libglib2.0-0 2.50.3-2
ii libgtk2.0-0 2.24.31-2
ii libjpeg62-turbo 1:1.5.1-2
ii libnotify4 0.7.7-2
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpng16-16 1.6.28-1
ii libsm6 2:1.2.2-1+b3
ii libstdc++6 6.3.0-18
ii libtiff5 4.0.8-2+deb9u1
ii libwxbase3.0-0v5 3.0.2+dfsg-4
ii libx11-6 2:1.6.4-3
ii libxxf86vm1 1:1.1.4-1+b2
libwxgtk3.0-0v5 recommends no packages.
libwxgtk3.0-0v5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Sep 16, 2019 at 09:30:42AM +1200, Olly Betts wrote:
> On Thu, Dec 14, 2017 at 06:25:34PM +1300, Olly Betts wrote:
> > You says this works for 3.0.3.1, but upstream says:
> >
> > | This is not trivial to backport, wxConvWhateverWorks doesn't exist in 3.0
> >
> > And that indeed seems to be the case, so we don't actually have a patch
> > we can use, hence I've removed the "patch" tag.
> >
> > Upstream are open to a patch which does backport this, but it's not a
> > one line change. For more info, see:
> >
> > https://trac.wxwidgets.org/ticket/16206#comment:10
>
> There are decent workarounds for this bug (set the locale, or use the
> char** overload of wxExecute) and no signs of interest in backporting
> the changes so I'm going to mark this as "wontfix".
>
> If the fix is backported and merged to upstream's WX_3_0_BRANCH we can
> pick it up for Debian before the next 3.0.x release (our packages are
> actually already tracking upstream's branch since 3.0.x releases are so
> infrequent).
The upstream ticket for this is still open, but nobody's shown any
sign of working on backporting the patch and it's not a simple patch to
backport so I don't think a backport is likely. I wouldn't bet on there
being another 3.0.x release from upstream even.
Upstream have recently released wxWidgets 3.2.0 which contains the fix
for this, and Scott's working on packaging that. Once that's in
unstable we'll be encouraging wxwidgets3.0-dependent packages to
transition to it and the wxwidgets3.0 packages will be firmly in
maintenance mode until they can actually be removed.
This bug is already tagged "wontfix" so I'm going to close it now.
Cheers,
Olly
--- End Message ---