Hi,
On Thu, Sep 25, 2014 at 4:06 AM, Goswin von Brederlow wrote:
> do we realy need a libzmq.so.3 in Jessie? Upstream is preparing a new
> stable version now with libzmq.so.4. Given that the breakage between 3
> and 4 is minimal (easy to port your software, most just works) do we
> need to mainta
Source: zeromq3
Version: 4.0.3
Followup-For: Bug #743508
Hi,
do we realy need a libzmq.so.3 in Jessie? Upstream is preparing a new
stable version now with libzmq.so.4. Given that the breakage between 3
and 4 is minimal (easy to port your software, most just works) do we
need to maintain 2
> Reverse dependencies are anything but unrelated.
Hello julien, from the point of view of the release team.
What should be do now ?
to my opinion, all we have to do is to upload
zeromq3 with this ugly but necessary +really versionnumber
4.0.3+really-3.2.4-1
then the problem should be fixed onc
On Sat, May 17, 2014 at 07:33:04 +0200, Tobias Frost wrote:
> IMHO the severity should be raised to critical as it breaks unrelated
> software.
>
Reverse dependencies are anything but unrelated.
Cheers,
Julien
signature.asc
Description: Digital signature
you can find all the information about this breakage in the bug #743508.
>
> So my question is how to deal with this mess ?
>
> thanks
>
>
> Frederic
>
>
(CC'ing the bug)
Well, I think the procedure was already laid out in the bug...
Epoch or a ugly version
Hello, so it seems that upstream agreed on the ABI breakage.
The importance of this bug should be raised, this is now RC.
We should ask the release team how to deal with this mess...
Do you agree with this ?
Cheers
Frederic
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
There are other incompatibilities between ZMQ 3 and 4 as well. The
event messages sent as a result of creating a socket monitor with
zmq_socket_monitor() have a completely different format in the two
versions, and have to be treated differently in code. (In ZMQ 3 the
message consists of one f
Hello
I discuss with the tango upstream, Indeed this can fix the problem.
BUT this is a real API breakage from the zeromq3 upstream.
I think that the so number is wrong. instead of
4:0:1 -> libzmq.so.3.1.0
it should be
4:0:0 -> libzmq.so.4.0.0
here are all the revers dependencies of libzmq3
On Mon, Apr 7, 2014 at 8:34 PM, PICCA Frederic-Emmanuel
wrote:
> this is not pytango but the tango library
Ah, OK.
>> The previous maintainer already uploaded 4.0.4 to unstable, there's
> no easy way to get back to 3.x .
>
> Yes usually we end up with this ugly 4.0.4.really.3.2.4 version number.
Hello László
this is not pytango but the tango library
picca@mordor:~/Debian/main/tango/tango/lib$ grep -ri inproc
cpp/server/tango_const.h:#define CTRL_SOCK_ENDPOINT
"inproc://control"
> The previous maintainer already uploaded 4.0.4 to unstable, there's
no easy way to get back
Hi Frederic,
On Mon, Apr 7, 2014 at 6:07 PM, PICCA Frederic-Emmanuel
wrote:
> Here is what you can find in ZMQ 4 release notes at [1]
[...]
> As you can guess, Tango depended on inproc connects failing when starting the
> event system!
It seems it doesn't use inproc :
path/pytango-8.1.1$ grep -
Here is what you can find in ZMQ 4 release notes at [1]
"You can now connect to an inproc:// endpoint that does not already exist. See:
tests/test_inproc_connect.cpp. NOTE: this is a breaking change in the API. If
your application depended on inproc connects failing, you must change it to try
t
This makes me wonder if there shouldn't be a libzmq4 package for the 4.x
series while leaving the libzmq3 for the 3.x series.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: libzmq3
Version: 4.0.4+dfsg-2
Severity: normal
Dear Maintainer,
After upgrading libzmq3 to 4.0.4+dfsg-2, the following stops working:
~$ python
>>> import PyTango
>>> dev_name = 'sys/database/2'
>>> dev = PyTango.DeviceProxy(dev_name)
>>> cb = PyTango.utils.EventCallBack()
>>> id = de
14 matches
Mail list logo
