Hello Olly, On Sat, Sep 13, 2014 at 5:10 PM, Olly Betts <o...@survex.com> 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.
the switch to the git snapshot was done because it seemed to include supports to wx3.0 in the unreleased code. > 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. > > Also, upstream's response to the forwarded ticket might be more useful > if you could show it happens with wx2.8 too. > > I tried rebuilding 2.3.1+git1a369e47-1 with wx2.8 myself, but I couldn't > trigger this behaviour from either the package in sid or my rebuilt > version (I tried switching between tabs over and over as described > above), so that's rather inconclusive. I wasn't connected to any > networks though, so that's perhaps why it didn't manifest. > > 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. Is there any chance you can give us a hand in fixing amule to support wx3.0? Upstream has only partially ported the code to it, and they are not actively working on it atm. IT would be a shame to ship Jessie without amule, but i dont have the resources to port amule to wx. I can consider getting back to 2.3.1-11 instead of the git snapshot if that makes the effort easier. Thanks & Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
