On 20/04/16 00:33, Julian Taylor wrote: > On 13.04.2016 15:39, Julian Taylor wrote: >> On 04/13/2016 03:24 PM, Emilio Pozuelo Monfort wrote: >>> On 29/03/16 19:10, László Böszörményi (GCS) wrote: >>>> Hi Julian, >>>> >>>> On Sun, Mar 20, 2016 at 12:27 PM, Julian Taylor >>>> <jtaylor.deb...@googlemail.com> wrote: >>>>> On 20.03.2016 11:11, László Böszörményi (GCS) wrote: >>>>>> Sorry, my life was chaotic. Yes and no, checked it. First, there's a >>>>>> new upstream version of pyzmq (15.2) for two months. It seems to be >>>>>> security related according to the release log[1]: >>>>>> - FIX: unicode/bytes bug in password prompt in zmq.ssh on Python 3 >>>>>> - workaround overflow bug in libzmq preventing receiving messages >>>>>> larger than MAX_INT >>>> [...] >>>>> The latest version does unfortunately not fix the problem. It is also >>>>> not security related, it just could not send large data due to bugs in >>>>> zmq. >>>>> I guess a good approach would be to bisect zmq to see what they changed >>>>> to cause it. >>>> Just a friendly ping; could you test the latest Git master if that >>>> fixes the hang and/or could you ask upstream for advice? Should I do >>>> it? It seems it constantly get fixes that may be relevant. >>> >>> The package is team maintained, so I would say go ahead and do a team >>> upload. >>> >> >> I see nothing in git that might be related and I'm not a fan of just >> doing a guess upload but if you like go ahead. >> Note that you have to disable the new large send test as it will fail on >> 32 bit and possibly swap on 64 bit. >> I still need to get porterbox access before I can look at it, but if >> someone can bisect libzmq before that happens for me would be great. >> > > here is what I have been able to figure out on powerpc, not much > unfortunately. > https://github.com/zeromq/pyzmq/issues/838 >
Looks like your last upload fixed the build on most architectures. However the package still failed to build on arm64. https://buildd.debian.org/status/package.php?p=pyzmq Cheers, Emilio