[Python-modules-team] Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done
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. Cheers, Laszlo/GCS ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done
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: >> On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort >> <po...@debian.org> wrote: >>> 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]: [...] > 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. Still any reason not to update it for Sid? Can you try Git master branch for building? That contains several fixes. While the same company develops ZeroMQ and the Python bindings as well, do you have contact with their Python team? It may worth to ask them, they may know what's the cause of the hang is. Regards, Laszlo/GCS ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done
On Sun, Mar 20, 2016 at 10:56 AM, Emilio Pozuelo Monfort <po...@debian.org> wrote: > On Tue, 15 Mar 2016 23:37:26 +0100 > =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <g...@debian.org> wrote: >> On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor >> <jtaylor.deb...@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. Regards, Laszlo/GCS [1] https://pyzmq.readthedocs.org/en/latest/changelog.html ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#818265: Bug#818187: zeromq3 migrated without any transition being done
On Tue, Mar 15, 2016 at 10:26 AM, Emilio Pozuelo Monfort <po...@debian.org> wrote: > On 14/03/16 22:03, Emilio Pozuelo Monfort wrote: >> Looks good. No problem and thanks for reacting that fast! > > I scheduled the binNMUs last night and things are going well. The only issue > seems to be pyzmq, see #818265. This is known to pyzmq upstream[1] for about three years. It happens on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While timer_create() [4] is in librt, the standard GNU C library, it seems pyzmq miss to link with it on the failing architectures. User reports says that 'pip install pyzmq --install-option="--zmq=/usr/lib"' forces the linking. I don't know how pass it to setup.py (not using pip directly) and the path should be multiarch aware for us. Hope this helps, Laszlo/GCS [1] https://github.com/zeromq/pyzmq/issues/391 [2] https://github.com/zeromq/pyzmq/issues/468 [3] https://github.com/zeromq/pyzmq/issues/658 [4] http://man7.org/linux/man-pages/man2/timer_create.2.html ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#764493: python-eventlet 0.15.2-1 to Sid/Jessie
Hi Ivo, On Wed, Dec 24, 2014 at 5:52 PM, Ivo De Decker iv...@debian.org wrote: On Fri, Nov 14, 2014 at 11:12:22PM -0500, Scott Kitterman wrote: Now that we are in Freeze, this is pretty unlikely. Any objection to just uploading the Ubuntu patch so we can close the RC bug? This looks like the obvious way to go. Laszlo, what do you think? Prepared the updated package. Final and clean build is in progress, when it's done I'll upload it to Sid. Then I can ask for a freeze exception and let it migrate to Jessie. Cheers, Laszlo/GCS ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#764493: python-eventlet 0.15.2-1 to Sid/Jessie
Hi, Thomas packaged v0.15.2 and uploaded to experimental. In my opinion it should be uploaded to Sid and let migrate to Jessie. The rationale behind is the following: - it handles connection socket timeouts and contains several bugfixes[1] without adding too much new code, - it doesn't have any bugreports against experimental, - it's part of Fedora 20 and 21, as well as RHEL7 as EPEL (extra package repository)[2] without any problem. The sslwrap.diff fix that Matthias adds in #764493 [3] still applies however. Should I upload it or do you have objections? Cheers, Laszlo/GCS [1] https://github.com/eventlet/eventlet/blob/master/NEWS [2] http://pkgs.fedoraproject.org/cgit/python-eventlet.git [3] https://bugs.debian.org/764493 ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#684852: missing egg-info in python-greenlet cause FTBFS of python-eventlet in Wheezy
unarchive 640577 tag 640577 wheezy affects 640577 python-eventlet thanks Hi, The addition of egg-info file to python-greenlet still affects python-eventlet . As the former bugfix do not migrate to Wheezy due to an other RC bug in python-greenlet . I plan to NMU[1] this to wheezy-proposed-updates. Regards, Laszlo/GCS [1] http://www.barcikacomp.hu/gcs/python-greenlet_0.3.1-2.1.dsc ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
