+1
* verified checksums and signatures
* build from sources
* successfully ran Qpid Broker system tests for AMQP 1.0 with proton 0.22
staged artefacts
On 13 September 2017 at 15:35, Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid Proton-J 0.22.0 release,
> pleas
Thank you Rudyy,
Unfortunately, I don't have any extra information to share. May be the stop
script should be updated to check output of kill command to confirm the process
is still here.
Regards,
Adel
From: Oleksandr Rudyy
Sent: Friday, September 8, 2017
On Thu, Sep 14, 2017 at 11:04 AM, Philipp Eib wrote:
> Hi Ken.
>
> Thanks for your answer.
> I installed it from standard 16.04 repo.
> I have now added the Qpid PPA, but it seems to only contain a
> "python-qpid-proton" package, but no "python3-qpid-proton":
>
> $ apt-cache showpkg python-qpid-p
+1
* ran apache-rat check on the source distribution
* built from source and ran proton-j test suite (on Oracle JVM
1.8.0_144 on Mac OS X 10.11.6)
* tested staged maven artefacts against Java Broker (master) with the
systests suite in AMQP 1.0 profile.
No problems encountered
On 14 September 201
Hi Ken.
Thanks for your answer.
I installed it from standard 16.04 repo.
I have now added the Qpid PPA, but it seems to only contain a
"python-qpid-proton" package, but no "python3-qpid-proton":
$ apt-cache showpkg python-qpid-proton
Package: python-qpid-proton
Versions:
0.17.0-1xenial+qpid1
Hi Philipp,
On Thu, Sep 14, 2017 at 9:16 AM, Philipp Eib wrote:
> Hi,
>
> what do I need to set to build the proton bindings for python3 instead of
> the default python2?
>
>
>
> Background:
>
> I need Proton with SSL support. Unfortunately, the python3-qpid-proton
> package for Ubuntu is not b
Hi,
what do I need to set to build the proton bindings for python3 instead of
the default python2?
Background:
I need Proton with SSL support. Unfortunately, the python3-qpid-proton
package for Ubuntu is not built with SSL support => I get an error
"SSLUnavailable: amqps: SSL libraries not fo
I'd be happy to cut a 1.37.0 release as soon as master is in a
position to do so, I'd definitely say it is overdue. Last I attempted
it, there were some open issues which seemed like they needed resolved
first, and there are probably a couple more now that either need
resolved or someone with knowl
+1 (built from source, ran tests)
-- Rob
On 14 September 2017 at 13:02, Gordon Sim wrote:
> On 13/09/17 15:35, Robbie Gemmell wrote:
>
>> I have put together a first spin for a Qpid Proton-J 0.22.0 release,
>> please test it and vote accordingly.
>>
>
> +1, rand source build and tests with no i
On 13/09/17 15:35, Robbie Gemmell wrote:
I have put together a first spin for a Qpid Proton-J 0.22.0 release,
please test it and vote accordingly.
+1, rand source build and tests with no issues.
-
To unsubscribe, e-mail: users
Hi,
Short version:
Please can I request/vote/beg for a release of qpid-cpp-1.37 soon? There
are pending fixes that we would very much like to have in production.
Long version (read: sob-story)
One such example is that we're suffering at the hands of this issue:
https://issues.apache.org/jira/brow
Hi all,
I'd like to share some ideas of mine about deploying custom topologies of
qdrouterd accross a set of nodes. This is probably a general discussion to
have regarding the various orchestrators (Puppet, Ansible, ...).
I don't know if there's a real demand of deploying custom topologies but f
12 matches
Mail list logo
