| Age | Commit message (Collapse) | Author |
|---|
|
There was common situations where two provider instances where running
in parallel. And was creating weird errors (like getting wrong api_uri)
because the bootstrap deferreds were global but the Provider objects
not.
I don't like much singletons, but I think now is simpler than before.
- Resolves: #9073
|
|
we make a distinction between the system-wide bitmask-root, which should
be placed there by the maintainers of whatever packages your
distribution uses, and the bitmask-root that is placed by the bundles
(using polkit).
since the bundles copying over the helper from user-writeable folders
is a potential attack vector, we prefer to use the package's version if
present.
also, if we cannot find either, we abort the launching of the VPN. we've
discussed that this might move to the service initialization instead,
but I think the cases in which this is needed should be rare.
I fix also a corner-case in which we were using getcwd() at import time.
if you execute code and then remove the installation path, this will
raise a traceback in bitmaskctl. I think it's nicer to catch the error
properly when starting.
|
|
the released soledad packages didn't list soledad-common as a dependency
for client.
this change can be reverted after releasing soledad 0.10.4
-Resolves: #9065
|
|
|
|
|
|
the package from docker was being copied with the `dist` name.
|
|
|
|
|
|
|
|
Short descriptions should be unique.
Related: #9033
|
|
The menu item specifies a command which is not available in the package. In
most cases this is a typo or after you moved a binary around, but forgot to
update the menu file.
I've moved the menu file to be in the bitmask-qt package.
Related: #9030
|
|
The package declares a depends on a virtual package without listing a real
package as an alternative first.
Its not necessary to have an alternative, but if there is a real package
providing that virtual package that most users will want to use, its better to
have one.
Its good to have a specific one set for build-dependencies, so that builds are
consistent.
Picking policykit-1-gnome as the suggested, but it could be any.
Related: #9033
|
|
The debian/rules file sets the DEB_BUILD_OPTIONS variable, which will override
any user-specified build profile.
We should be setting DH_BUILD_MAINT_OPTIONS.
-Related: #9033
|
|
|
|
|
|
|
|
|
|
in this way, it gets nicely renamed with the version number and hash.
|
|
|
|
- cross-refs to bitmask.net
- wording
- missing deps
|
|
|
|
Also, allow to pass a different repo to the build-in-docker script.
- Resolves: #9089
|
|
|
|
|
|
|
|
the page was becoming too cluttered.
|
|
|
|
|
|
|
|
- Related: #9079, #7566
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Related: #9033
|
|
- Related: #9033
|
|
- Resolves: #9060
|
|
- Resolves: #9077
|
|
Resolves: #9072
|
|
we're doing something that shouldn't be done, that is relying on private
methods of the imap server implementation.
until I get to cleanup properly and submit patches for the several things
we're patching in the imap server implementation, keeping up with the
evolution of the imap server implementation is the only thing to do.
specially when we want to get 0.10 out of the door asap.
|
|
- Resolves: #9084
|
|
Relates to #8918
|
|
|
|
whoever wrote this in the first place needs to get introduced to
import-time initialization, even if it was me. one of the nastiest
python gotchas in my opinion :)
|
|
just to make the logic clear.
we should probably check that the file is not empty and it has valid
json (sanitized against the spec).
|
|
(add some extra line to force tests to run again)
|
