Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

On 04.12.2016 14:14, Luca Boccassi wrote: > >> But on how to fix this. Given [0] you seem to be just passing out the >> pointer to your internal buffer written without padding out to the user >> via zmq_msg_data (?) >> >> The documentation of that function states that you must not access >>

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

Hello, I just opened a bug for tango https://github.com/tango-controls/cppTango/issues/312 what is the deadline where we can take the decision to upload or not zeromq 4.2.0 into Debian testing ? This will let also some time in order to check if this 4.2.0 do not have other size effect of

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

Hi Picca, Luca, On Wed, Nov 23, 2016 at 3:25 PM, PICCA Frederic-Emmanuel wrote: >> This is very unfortunate, but as explained on the mailing list, this >> behaviour was an unintentional internal side effect. I didn't quite >> realise it was there,

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

Hello Luca > This is very unfortunate, but as explained on the mailing list, this > behaviour was an unintentional internal side effect. I didn't quite > realise it was there, and so most other devs. I understand, I just wanted to point that the synchrotron community invest a lot of efforts in

Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

On Wed, 16 Nov 2016 08:55:47 +0100 picca wrote: > Source: zeromq3 > Severity: important > > Dear Maintainer, > > It seems that zeromq 4.2.0 brakes the tango package. > this is why I fill an important bug in orer to block migration testing. > > You can have a look