| Age | Commit message (Collapse) | Author |
|---|
|
- Related: #7583
|
|
- Resolves: #7568
|
|
|
|
from debian stretch on, gpg will be a symlink to gpg2.
this is currently failing if one uses dpkg-divert to make gpg2 provide
/usr/bin/gpg.
this solution just attempts to use gpg2 binary if the search for gpg
binary fails.
- Resolves: #7563
- Releases: 0.9.1
|
|
When the error happens too quickly, the errback is called before the
assign of the callLater. And in the errback we cancel that call which
gives an error.
- Related: #7451
|
|
- Resolves: #7503
Signed-off-by: Ivan Alejandro <ivanalejandro0@gmail.com>
|
|
- Related: #7471
|
|
there was a bug in plaform that made webapp not serve correctly the smtp
certificates. with this fallback, we try to support platforms < 0.8,
although we should deprecate this behavior in bitmask 0.10
|
|
|
|
the second callback was actually broken, not being called when it was
supposed to be.
the reason is that IncomingMail.startService returns a deferred which
callback is called with the loopingCall instance only when the
loopingCall is stopped.
|
|
Is valid for a provider not to provide locations for their gateways.
- Resolves: #7281
|
|
|
|
|
|
s/self/sync
|
|
Replace logging.getLogger with custom get_logger.
Remove some unneeded dependencies and reorder other.
|
|
due to remaining bits that had not been changed after a refactor.
- Resolves: #7093
|
|
- Related: #6359
|
|
* Instead of checking if soledad is still syncing for the timeuot cancel
the delayed call.
* Count retries properly.
* Now soledad sync only returns SoledadError (#6981).
|
|
Replace the hardcoded port '1194' for the port specified in
eip-service.json.
Choose the best port to use according which one is enabled in the
eip-service.json file
Resolves: #6541
|
|
This concern is addressed by the following mail pullreq, that will be
into 0.4.0 release:
https://github.com/leapcode/leap_mail/pull/175
By the way, it is really funny that I cannot tell if this comment was
written by meskio, as the blame says, or if I was the original author of
the remark. I should stop drinking so much coffee.
|
|
The code was using 'fail' which is not a Deferred method.
- Resolves: #6772
|
|
|
|
the set_proxies_cb function in backend/components expects to have access
to these public properties.
|
|
This closes: #6658 and #6691
|
|
|
|
factory.do_Stop will handle this now.
|
|
we should deal with this with pure deferreds
|
|
|
|
|
|
From kali: add some notes about the improper handling of the mailbox
required to initialize the account, and draft some notes about how
to improve this in next iterations.
|
|
|
|
This causes (on certain scenarios) the app to segfault and it is really
hard to debug.
|
|
Remove srpauth obsolete tests.
Remove providerconfig obsolete test.
Set as mandatory the signaler object on ProviderBootstrapper and
EIPBootstrapper.
Closes #6631.
|
|
This reverts commit 93750f2371555ad0c769c62c1bd179e2b96c282c.
|
|
|
|
Closes #6150.
|
|
Conflicts:
pkg/tuf/release.py
relnotes.txt
|
|
|
|
|
|
This reverts commit 7fcc4f40eaa8214de8ae20cd71d173337ad64290.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes: #4035
This falls in the "quick" workaround category.
A proper state machine that extends the four basic connection states
is hence needed. We have to accomodate design to have a
connection-oriented state machine in the backend (I would favor a
twisted protocol for this), and a more lightweight one that conducts
the gui-level changes (ie, change the actions / buttons / labels
accordingly).
Since this "cancel" functionality has been long postponed, I chose
to do one more ugly hack here, that is, show and hide dance with a
button that just calls the bitmask-root to kill the vpn process. It
should work well enough until we get to the reorganization needed for a
clean process control for eip.
|
|
|
