Hi Picca, Luca, On Wed, Nov 23, 2016 at 3:25 PM, PICCA Frederic-Emmanuel <frederic-emmanuel.pi...@synchrotron-soleil.fr> 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, and so most other devs. > > I understand, I just wanted to point that the synchrotron community invest a > lot of efforts in order > to provide a tango stack into Debian Stretch. As I understand (and remember) tango uses internal structures of zeromq. Am I right? If so, can it be rewritten in a way to be more zeromq version independent?
> It would a big fail for use if Debian stretch were released without tango. I would like to keep it, even if popcon score seems to be low. >> How much work would it be to change tango to avoid relying on aligned >> internal recv buffers? > > I spoke with the tango upstream, and they told me that this change is not > that trivial. > This is unfortunate that it is so late in the release cycle of Debian. > I think that they will not have the time to do this change before the 5 > febuary. But it's not the first time when they are asked not to use internal zeromq structures - not the first time tango has problems after a zeromq update[1]. > I will keep you informed if something moves from their part. Please do. > BUT I beg the zeromq3 maintainer to stick with 4.1.5 for Stetch. It's a bit hard to be equitable, which hand to bite: have an old zeromq version maybe without security support or lose tango from Stretch. :( Regards, Laszlo/GCS [1] https://bugs.debian.org/743508
