| Age | Commit message (Collapse) | Author |
|---|
|
It is not clear why the pinning was made in the first place, and we need
to downgrade because the current pyzmq version packaged for jessie is
14.4.0. Pinning to a higher version that is not available in debian
causes problems when using python entrypoints for Soledad Server (as we
do now).
|
|
|
|
|
|
This commit removes the dep introduced in 5e12233 by just importing some tiny
bit of dirspec code.
The previous change was introduced because:
* pyxdg did not account for Mac OS specifics, i.e. using ~/Library/
directory structure instead of .config (see:
https://leap.se/code/issues/3574).
* dirspec does the correct thing for xdg on Mac OS.
* u1db depends on dirspec anyway.
The problem is that dirspec is not maintained and published on pypi, what
forces us to download it from an URL and add exceptions to be able to pip
install it.
As we are removing dependence on u1db on other modules, we can also remove it
here. To workaround the Mac OS problem, we just add some code from dirspec to
ensure we get the correct directory on Mac OS.
|
|
Also added dirspec directly to the setuptools for now,
because it needs the dependency along with the url, but pip
would break if it had both
|
|
Leap pycommon will now be installed in editable mode
when you use pip install, so that you can run the tests
and develop using only pip
|
|
I also added a conditional to the setup.py so
that python setup.py develop can be used even
with the dirspec url
|
|
|
|
While testing the way that its implemented now, I found out that no check
is being made on certificate attributes against the host.
I found this simple way of creating a BrowserLikePolicyForHTTPS using
a self signed cert and it worked on my test. I used test_https from
Soledad for checking this (which we are fixing on another branch).
Also, we don't want to depend on twisted for other things than
leap.common.http.
|
|
Before this commit, protobuf and protobuf.socketrpc were used to serialize and
transmit messages between events clients. This change implements a simpler ZMQ
client/server events mechanism that uses ZMQ sockets for transmitting messages
from clients to server and to redistribute such messages to subscribed
clients.
Closes: #6359
|
|
Implements an HTTP client the twisted way, with a focus on pinning the
SSL certs.
* Related: #6506
|
|
|
|
* Use requirements.pip
* Update reqs
|
|
|
|
|
|
|
|
|
|
Conflicts:
pkg/requirements.pip
setup.py
|
|
|
|
|
|
|
