There were 7 binding and 1 non-binding +1 votes, with no other votes
received. The vote has passed.
I will re-tag the 0.10-rc3 tag in the repo as 0.10 proper, add the
release files to the dist release svn repo, and release the maven
staging repo. The website will be updated later after the artifac
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695989#comment-14695989
]
Andrew Stitcher commented on PROTON-952:
It may be a "cmake bug" in that cmake doe
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-952.
Resolution: Fixed
> Building Proton with python 2.6 and python 3.4 on Travis CI finds and li
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reopened PROTON-952:
Assignee: Andrew Stitcher (was: Ken Giusti)
> Building Proton with python 2.6 and python
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-952:
---
Fix Version/s: 0.11
> Building Proton with python 2.6 and python 3.4 on Travis CI finds and li
[
https://issues.apache.org/jira/browse/PROTON-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695979#comment-14695979
]
ASF subversion and git services commented on PROTON-952:
Commit 23
I've now figured out the issue (and it's an instructive problem):
PROTON-979: [1]
It seems that both OpenSSL and Cyrus SASL have interacting global
state. If SASL gets to initialise libcrypto first then when the SSL
code tries to do it it fails.
Just another emphasis that neither openssl nor Cyr
I vote +1:
I've tested proton-c & python on:
Ubuntu 12.04 (amd64)
Ubuntu 14.04 (amd64/i686)
Raspberry Pi2 (Raspbian Jesse)
FreeBSD 10.1p17
Windows 8.1 with Visual Studio 12 (2013)
[Some of these test have had Java & tox as well but it's been uneven)
And modulo some (severe) irritations (see the
Great, well done figuring it out!
Care to vote yet? :)
Robbie
On 13 August 2015 at 21:16, Andrew Stitcher wrote:
> I've now figured out the issue (and it's an instructive problem):
>
> PROTON-979: [1]
>
> It seems that both OpenSSL and Cyrus SASL have interacting global
> state. If SASL gets to
Andrew Stitcher created PROTON-979:
--
Summary: build tests fail if Cyrus SASL otp mech is installed
Key: PROTON-979
URL: https://issues.apache.org/jira/browse/PROTON-979
Project: Qpid Proton
On 08/13/2015 03:20 PM, Robbie Gemmell wrote:
To clarify, my run was also using the x86_64 / amd64 version, using a VM.
Neither of us have been able to reproduce what Andrew saw, so unless
we can get a better idea what it is specifically then I am inclined to
say that we proceed. If there is a
To clarify, my run was also using the x86_64 / amd64 version, using a VM.
Neither of us have been able to reproduce what Andrew saw, so unless
we can get a better idea what it is specifically then I am inclined to
say that we proceed. If there is an issue and it can be identified,
I'm sure it will
I ran the tests under Ubuntu 14.04 (for amd64) running an x86_64 Linux
kernel (using Docker). All of the tests, including the SSL tests pass.
-Ted
On 08/13/2015 09:56 AM, Robbie Gemmell wrote:
I have run up a fresh Ubuntu 14.04.3 install didn't see any issues
(once I figured out what packages
I have run up a fresh Ubuntu 14.04.3 install didn't see any issues
(once I figured out what packages to install to get the tests all
running). Can you elaborate on the problem you are seeing?
Robbie
On 12 August 2015 at 22:41, Andrew Stitcher wrote:
> I've tested proton-c on ubuntu1404, ubuntu12
14 matches
Mail list logo
