Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-123005675
I've raised [PROTON-951](https://issues.apache.org/jira/browse/PROTON-951)
and [PROTON-952](https://issues.apache.org/jira/browse/PROTON-952) - which are
related b
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122924850
@astitcher ok great
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have th
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122922144
@gemmellr I'm going to try to characterise the python 3 build issue a bit
better then raise a JIRA.
---
If your project is set up for it, you can reply to this e
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122902052
@dnwe Yeah, I'm a bit lost with these bits I'm afraid hence the sugestion
of mentioning any issues more directly on the list so those with a clue are
aware somethin
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122900045
@gemmellr the error message for py26 is quite odd. It seems like its
failing on the new "compile proton from python if libqpid-proton isn't
available to link against" t
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122896223
Do the earlier comments mean that it no longer tests on 2.6 but did
previously? Is that perhaps because the newer infrastructure doesn't include
2.6? or perhaps sin
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/47
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122437243
Ok. :+1. Ship it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fea
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122436754
The tox thing is the bit I'm shakiest about - it seems to find 3 out of
the 4 pythons (not 2.6 I think) for some reason. I experimented with a
matrix test wh
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122435936
Changes look reasonable to me. Faster sudoless docker builds would be cool.
You dropped the PYTHON_DIRS bit which was for tox to locate the various
Python inte
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/47#issuecomment-122435378
It looks to me that the appveyor failure is due to some incidental issue
with the service.
---
If your project is set up for it, you can reply to this email and h
GitHub user astitcher opened a pull request:
https://github.com/apache/qpid-proton/pull/47
NO-JIRA: Change travis configuration to use container based builds
This is specifically for comment from @dnwe - I'm proposing to change the
travis build config to use containers, but I've st
12 matches
Mail list logo
