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

Control: forwarded -1 https://trac.wxwidgets.org/ticket/16206

While the patch is small, it changes established behaviour.  And though
arguably the current behaviour is not helpful for modern Linux, we need
to think carefully before diverging from upstream on such things.

So I've suggested upstream should backport this to 3.0.x as I'd like to
see if they had a reason for not backporting this change already.

It seems this issue can be avoided by setting the locale, or by using
the char** overload of wxExecute - if upstream aren't going to fix
this in 3.0.4, then apps would be well advised to make sure they do
one of these things so that they work everywhere, rather than only on
Debian.

Cheers,
    Olly

Control: tags -1 - patch

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

Cheers,
    Olly

Control: tags -1 +wontfix

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).

Cheers,
    Olly

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