GitHub user gmile opened a pull request:
https://github.com/apache/couchdb/pull/431
build: support OTP-19.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gmile/couchdb allow-1.6-with-new-erlang-19.0
Alternatively you can
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal sure! Just pushed a commit with updated `.travis.yml` config, we'll
know if all good in an hour and a half
---
If your project is set up for it, you can reply to this email and have
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal yeah, so it appears build is broken with `18.3` and `19.0`,
although it compiling couchdb 1.6.1 against `19.0` from OS X worked locally.
I'm looking at the [log for failed 19.0
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
I'll stop the current build on CI, comment out 17.0, R16B03-1, R15B03,
R14B04 and will try to see what's going on here with 18.3 and 19.0.
---
If your project is set up for it, you can rep
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal how about adding a line `^erlang-19.0-nonroot.tar.bz2` line to
`https://github.com/apache/couchdb/blob/master/license.skip`? It seems even
easier, unless you would prefer not to populate the
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal no problem at all, will do that. Thanks for helping with this!
---
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
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal something's still not right, but this time it's vise-versa: builds
for 19.0 and 18.3 have passed, but all others have failed. Maybe this gives any
clue regarding an old fix you&#x
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
Probably this fails now:
```
The command "rm erlang-*.tar.bz2" exited with 1
```
---
If your project is set up for it, you can reply to this email and have your
reply
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@kxepal and it's green, finally
---
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
enable
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@dch no worries, no offence taken! Please go ahead with whichever path
suites you, you're the maintainer after all :)
---
If your project is set up for it, you can reply to this email and have
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@dch I _think_ it should be less work to revert + apply this PR. Otherwise
you'll have to cherry-pick changes, such as `.travis.yml`?
---
If your project is set up for it, you can reply to
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
Besides, I think this is missing from @dch's patch â
https://github.com/apache/couchdb/pull/431/commits/98ff0acdf04a8f0f29d066ae33f6e7332c024da9#diff-67e997bcfdac55191033d57a16d1408aR441
(tho
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@dch good to know!
> I'll tweak this line in configure.ac if that's ok:
Sure, go ahead and change that line. Just to clarify, I tested using
`19.0.1`, which yield
Github user gmile closed the pull request at:
https://github.com/apache/couchdb/pull/431
---
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 gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@dch haha, thank you! :)
---
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
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
@dch now that this was merged, will there be a point release in 1.6.x
branch? If not right now, are you planning to make one in future?
---
If your project is set up for it, you can reply to this
Github user gmile commented on the issue:
https://github.com/apache/couchdb/pull/431
> we have a nice 1.x.x branch
Ah I missed that, nice!
> good question, do you want to ask this on the dev list?
Sure! Can you share the link to dev list please?
17 matches
Mail list logo
