Hi Olly, Thanks for looking into this issue.
On Sat, 13 Sep 2014 13:10:17 Olly Betts wrote: > There are two big changes between 2.3.1-11 and 2.3.1+git1a369e47-1 - one > of them is indeed the switch to wx3.0, but the other is a switch to an > upstream git snapshot of amule. > > I think it would be prudent to rebuild 2.3.1+git1a369e47-1 against wx2.8 > and test if that has similar issues before blaming wx3.0 for these > problems. While they could be related to wx3.0, I've not seen such > issues in any other packages. I couldn't agree more that problem has to be better isolated. I re-built amule_2.3.1+git1a369e47-1 with "libwxgtk2.8-dev" and "wx2.8-i18n" (instead of "libwxgtk3.0-dev" and "wx3.0-i18n") and it works flawlessly for me while WX-3.0-linked version hands within few minutes of use. It seems pretty conclusive to me that in this case problems are indeed originated from WX-3.0 transition. Sorry. > I noticed wx upstream has applied a fix for the wxExecuteData issue > (http://trac.wxwidgets.org/ticket/16325) - I can apply that to the > wxwidgets3.0 package if you'd prefer to try updating 2.3.1-11 to work > with wx3.0. I'm not sure I qualified to comment regarding this issue... Perhaps it would be best for maintainer to decide... Since amule_2.3.1+git1a369e47 works well with WX-2.8 I hope it won't be too hard to fix it for WX-3.0. What choice do we have after all? -- All the best, Dmitry Smirnov. --- Science embraces facts and debates opinion; religion embraces opinion and debates the facts. -- Tom Heehler, The Well-Spoken Thesaurus.
signature.asc
Description: This is a digitally signed message part.
