[Python-modules-team] Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

Julian Taylor jtaylor.debian at googlemail.com
Sun Mar 20 11:27:58 UTC 2016

On 20.03.2016 11:11, László Böszörményi (GCS) wrote:
> On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort
> <pochu at debian.org> wrote:
>> On Tue, 15 Mar 2016 23:37:26 +0100
>> =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <gcs at debian.org> wrote:
>>> On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
>>> <jtaylor.debian at googlemail.com> wrote:
>>>> On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>>>  While I was checking the failing build logs, I see:
>>> build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
>>> function `main':
>>> timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
>>> collect2: error: ld returned 1 exit status
>>> It's not just the implicit declaration, but a linker error later. I
>>> can be wrong, but it seems it _may_ cause the test hang as there's no
>>> timer to look for / to wait its expiration. Sorry if it happens in
>>> normal logs as well; will check it tomorrow morning as it's almost
>>> midnight here. :(
>  Checked, it happens in normal build logs as well.
>> Got a chance to look at this?
>  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
> My computer is old and has problems; even the archive version hangs
> during self-tests. Still, it may help if Julian update the package to
> the latest version. With my Python Modules team member hat on, should
> I do it myself?
> Just for the record, upstream Git tree has even more fixes that not
> yet released as a new version.

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.

More information about the Python-modules-team mailing list