Hello,
Just found this discussion. We just released 4.2.0, sorry it took a while,
difficult times.
I hope the delay didn't cause you guys too much trouble.
The patch to use dynamic ports in the test looks very interesting, it's
something I wanted to fix for a while but never had to the time, so
This bug was fixed in the package zeromq3 - 4.1.5+git20160811+2fc86bc-
0ubuntu2
---
zeromq3 (4.1.5+git20160811+2fc86bc-0ubuntu2) yakkety; urgency=medium
[ Łukasz 'sil2100' Zemczak ]
* New upstream snapshot based release (2fc86bc) (LP: #1612240)
* debian/libzmq5.symbols:
- Up
This bug was fixed in the package zmqpp - 4.1.2-0ubuntu1
---
zmqpp (4.1.2-0ubuntu1) yakkety; urgency=medium
* New upstream release
* debian/copyright:
- Follow up on the license change to MPLv2
* debian/watch:
- Point to the new upstream location
* debian/patches/suppo
We don't want to pull this in as a completely separate source package;
that doesn't address the support problem, as it's precisely the "forked"
version that we would need to support.
Since there is no library transition here, and it sounds like the risk
of an ABI break before 4.2 releases is quite
I now re-checked zeromq trunk to see if any critical issues have been
found and fixed, but almost all the new commits in git are either
Windows-related, build-specific or documentation updates. So far it
looks that code-wise things are rather-stable.
Could we get a final decision here? The ubuntu-
There are a few possibilities. One is that we try to force an update to 4.2 no
matter when it's released, trying to push it into yakkety even after
release-day. The rationale would be that the snapshot is anyway closer to 4.2
than anything, so it would be more like a 'bugfix' than a new feature-
Ok. If 4.2 has been in limbo since May, it's possible it won't be ready
in time for 16.10 release. It's also possible that it will be released,
but it will unexpectedly introduce incompatibilities with the current
git snapshot. If either of these happens, what is the plan for handling
this?
--
Hey Steve!
So the zeromq crew was planning on starting the 4.2 release in May already, but
things seem to have been pushed back and back with still no concrete release
date. They're working on it still, also involving people from Debian, but there
is simply no release date as of yet. But the re
Hi Łukasz,
When you say the next stable release of zeromq3 is "planned in the
nearest future", when exactly is that?
Since there is also a plan to get unity8 into main properly for 16.10,
this would seem to imply pulling zeromq3 into main. So we would want to
make sure we can provide security su
** Description changed:
Please update zmqpp to version 4.1.2 with the following patch that I proposed
upstream (it got merged into their "develop" branch):
https://github.com/zeromq/zmqpp/pull/167/files
(alternatively, use master + my patch or develop branch of zmqpp).
This will req
** Description changed:
Please update zmqpp to version 4.1.2 with the following patch that I proposed
upstream (it got merged into their "develop" branch):
https://github.com/zeromq/zmqpp/pull/167/files
(alternatively, use master + my patch or develop branch of zmqpp).
This will req
11 matches
Mail list logo
