| Age | Commit message (Collapse) | Author |
|---|
|
Those files are no longer needed (nor present on the repo).
- Resolves: #7384
|
|
|
|
if __version__ is not properly assigned, provider tests were breaking
when parsing BITMASK_VERSION (which is None, where a string is
expected).
- Resolves: #7322
|
|
on the sumo tarball, the _version file for leap/bitmask submodule wasn't
being frozen, and hence BITMASK_VERSION was None. this was breaking the
provider tests w/o any clear error message.
- Related: #7322
|
|
Register to Soledad's sync (send and receive) events and display the
progress in the UI.
- Resolves: #7353
|
|
apply_updates.py applies the already downloaded files from the updates
folder and removes all the obsolete files from the bundle. It's meant
to be use by the pyinstaller bundle.
- Resolves: #7342
- Related: #5876
|
|
|
|
this is a bug in macholib, there's a missing letter in the plugins path, so
unless we fix this they cannot be loaded from the bundle.
See:
https://bitbucket.org/pydica/pyside-setup/commits/4b8be97e5a00b577fe30ce9aa7e5723ff2a66f94
Quoting from http://code.activestate.com/lists/pythonmac-sig/23278/:
"""
The problem might be this line:
@rpath/Contents/mageformats/libqtiff.dylib
The "i" from "imageformats" is missing!
This _might_ be related to the unusual case that "libqtiff" has no path
at all, or something else
is funny, and we end up with a name that will not be found at all.
Then the loader finds the plugin in the installed Qt, which causes it to
load everything
again from there.
"""
|
|
due to zmq, we are hitting the limit and getting app crashes.
- Resolves: #7319
|
|
thanks for making our lives easier during all this time, now we're
starting a relationship with pyinstaller.
maybe our roads cross again in the future.
|
|
we won't be using this for packaging though.
it can be useful to avoid installing it, although installing from wheel is
quite straightforward in osx.
|
|
|
|
|
|
|
|
|
|
The tests where using deferToThread to run without need, I remove it
and now it's easier to debug when one test fails.
- Resolves: #7343
|
|
--use-leap-wheels sets --trusted-host (remove it when we have a proper
cert) and WHEELHOUSE to https://ftp.lizard.leap.se
Until we get ftp.lizard cname, use lizard as the wheels server.
- Related: #7339
|
|
The new pyinstaller method will rule out the launcher, we need the
updater working inside bitmask client.
- Closes: #7291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generate_wheels uses $WHEELHOUSE to generate and store the wheels for
requirements.pip and requirements-testing.pip (if it exists).
pip_install_requirements.sh installs requirements.pip from them if
possible (if not, then it fetches them from pypi) or, if passed the
--testing flag, it installs requirements-testing.pip.
Related: #7327
|
|
|
|
|
|
to workaround the incompatibility problem with Qt libs found in ubuntu
|
|
there are a couple of manual steps needed
|
|
linux only, at the moment, but it's a good start :)
|
|
|
|
- update pip
- install base reqs
|
|
Is useful for new providers to be able to use the stable Bitmask
version with this flag to be able to use custom certificates.
- Resolves: #7250
|
|
|
|
|
|
this is part of a process to make the setup of the development mode less
troublesome. from now on, setting up a virtualenv in pure development
mode will be as easy as telling pip to just install the external
dependencies::
pip install -r pkg/requirements.pip
and traversing all the leap repos for the needed leap dependencies doing::
python setup.py develop
- Related: #7288
|
|
|
|
otherwise the module cannot be imported (in the pseudo-pkg produced by
the sumo tarball)
- Releases: 0.9.0
|
|
- Releases: 0.9.0
|
|
Also, do not raise assertionerror, log warning instead.
|
|
otherwise, events are not correctly registered
- Resolves: #7149
|
|
Fix:
If the logbook controller is not started the stop call will fail.
Trying to start it twice fails.
|
|
lemur/buildbot is intentionally off
|
|
- Resolves: #7284
|
|
|
|
|
|
|
|
Prevent locks caused by the zmq log handler reaching the zmq's HWM (High
water mark / buffer limit) and causing some components to block until
the buffer is empty (running the zmq handler for instance).
We run the zmq handler in the background all the time to prevent this.
- Resolves: #7222
|
|
some general notes about the QA process
|
