Refactor CI config to eliminate tox and use distro olm #311
Conversation
non-Jedi
force-pushed
the
ci-simplify
branch
7 times, most recently
from
c87c64f to
238b3df
Compare
|
@poljar python-olm tries to build olm when installed even if /usr/lib/libolm.so already exists. Do you know if there's a way to force it to use the already installed olm binary, or do we really need to continue staying on the path of building olm with each CI run even though a perfectly good olm library (but not python bindings) is available in Ubuntu 18.04? |
|
Huh? Where do you see it doing that? The only thing that python-olm knows how to build is its own module, that module does link against libolm. If you mean this line here: That means that the installed C libolm library is too old for the python bindings to build. |
|
Ah. Well crap. I obviously misread. Thanks. |
|
@poljar Are you planning on keeping https://pypi.org/project/python-olm/ up-to-date? It currently points to the archived github repo as the homepage instead of the olm repo, so I wasn't sure. |
Also now use python-olm from pypi instead of directly using the (now defunct) git repo.
|
Yes. Pointing to the old repo is a mistake. This is the official™ release and is up to date. |
non-Jedi
force-pushed
the
ci-simplify
branch
2 times, most recently
from
1da1c74 to
eee8f53
Compare
Sphinx minimum version bumped per sphinx-doc/sphinx#5870 (comment) since doc building currently fails on 3.7 CI.
3 participants
Closes #307, #308
Let's just hope CI actually passes for this PR.