| Age | Commit message (Collapse) | Author |
|---|
|
this has the ability to be used from the command line, although I'm
using it manually at the moment.
|
|
|
|
|
|
|
|
|
|
Great work by paixu, one step into the direction of winodows
reproducible builds. The installer doesn't work, but this probably has
to do with remaining bugs in the main qt app.
|
|
|
|
|
|
|
|
provide a environment that allows automated builds of windows installers
- prepare dockerized environment with wine, python, openssl, zlib and mingw
to build windows binaries from python sourcecode
- prepare dockerized environment with nullsoft installer
to build installers from binaries
- configure pyinstaller to build binaries
- configure nsis to build distributable executables for bitmask
- configure make all in pkg/windows that results in installers
- add documentation
- ico conversion from data/images
- avoid polluting / in docker image
- install dirspec and copy to wine env
- remove obsolete comments
- fix python path
- figure out that pip install leap.a and pyinstalling a leap.b does not work - so the build script fixes that
- rename dependencies to pyinstaller and move nsis code to installer
- build openvpn, export the binaries for further processing
- correct openvpn dependencies, fetch tap installer compatible with openvpn just built
- install tap-driver with nsis
- pyinstaller-build: fix mixed mkdir / show errors if there are some
- installer-build: prepare rw-copy, do not expose nsh files
- add openvpn_leap.exe to install directory so it gets picked up by nsis
- use setup.py to install bitmask to site-packages to have a version
- separate build directories for granular make
- copy all openvpn dlls to installer
- die to signal failure to parent makefile
- cache installDependencies for quick turn-arround times
- share openssl version between openvpn and pysqlcipher/other pip builds
- collect files during prepare for installer
- default to eip:false, mail:true
- configuration in pyinstaller-build.sh
- win64 tap drivers need special care getting removed from 32bit nsis
- correct registry key that identifies if we installed TAP
- extract version from git-tree, expose to wine python
- create nsh with version for build installer
- allow clean/dirty version with patches
- cleanup / indent / remove comments
- die when pysqlchipher patch failed
- add psutil in mingw compatible version
|
|
|
|
|
|
|
|
otherwise, it tries to open eip config.
- Resolves: #7538
- Releases: 0.9.2
|
|
|
|
|
|
The previous "fix" attempt with QT_GRAPHICSSYSTEM=native apparently
wasn't fixing the issue consistently.
This extra env var works 100% of the times by my tests though.
- Resolves: #8028
|
|
|
|
- mention the versions in the next relnotes
- add the leap_thirdparty_build to gitignore.
the build scripts are supposed to place the binaries here.
|
|
|
|
|
|
and replaces it with bitmask-logo.svg
- Releases: 0.9.2
|
|
In the latest snapshots, pixelated has migrated to use Account instead
of IMAPAccount.
Also, created an adaptor for Nicknym that allows to be initialized with
just the userid and the keymanager instance. This is ugly and has to go
when we converge on a single codebase (bitmask.core, hopefully).
|
|
|
|
|
|
this was the cause for the previous alpha releases keep insisting on
re-installing the helper files.
- Resolves: #7989
- Releases: 0.9.2
|
|
- Resolves: #8028
|
|
|
|
|
|
The thunderbird plugin will read the tokens from there.
- Related: #6041
|
|
This greatly simplifies the handling of the password in the thunderbird
extension.
- Related: #6041
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
currently, we're distributing the wheels for the pixelated modules under
downloads.leap.se.
bootstrap script tried to download the pixelated modules, but it fails
on python versions < 2.7.9, apparently.
as a workaround, I make the import of the pixelated modules a non-fatal
error by setting a flag, and doing the launching of the pix UA
conditional on a successful import.
- Related: #8009
|
|
|
|
|
|
fix docker readme to reflect the proper commands
|
|
- Resolves: #7990
|
|
|
|
|
|
|
|
otherwise, the configs are saved to the user home config folder.
|
